Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: e480c0d095f29e8508b0e47281cc3e4d6f30e939bd5a1fd9c780223012072cb7

Tx prefix hash: 1d85346fa220fdb7884128e06defcd156cc51bbed51bf3005f92133b95076b7a
Tx public key: da8dbdf3a6b3c5ac432c1db786fa9f50a6881d25e824ced5324a21729bb97d99
Timestamp: 1748851014 Timestamp [UCT]: 2025-06-02 07:56:54 Age [y:d:h:m:s]: 00:172:11:08:04
Block: 1296204 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 120944 RingCT/type: yes/0
Extra: 01da8dbdf3a6b3c5ac432c1db786fa9f50a6881d25e824ced5324a21729bb97d99021100000002bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1e224049ba885468694d83127e58080ae5a84d14c419ff0a2c441605affb56e9 0.600000000000 1783711 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1296214, "vin": [ { "gen": { "height": 1296204 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1e224049ba885468694d83127e58080ae5a84d14c419ff0a2c441605affb56e9" } } ], "extra": [ 1, 218, 141, 189, 243, 166, 179, 197, 172, 67, 44, 29, 183, 134, 250, 159, 80, 166, 136, 29, 37, 232, 36, 206, 213, 50, 74, 33, 114, 155, 185, 125, 153, 2, 17, 0, 0, 0, 2, 191, 81, 178, 162, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8