Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 890b166334527619d83e86300c582302227280d0baa5bdfd1fd2d709e6e826f0

Tx prefix hash: 5e7e13abe39bf8ddbfc328c4a90a1b7af92efd3e47abd08e4771755e442bdb70
Tx public key: ff0fbe1b0e8f198afb00180248721fcae7a4f1dac8f8d91200e7aac5a4245e4f
Timestamp: 1711348022 Timestamp [UCT]: 2024-03-25 06:27:02 Age [y:d:h:m:s]: 00:295:20:25:10
Block: 985848 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 211752 RingCT/type: yes/0
Extra: 01ff0fbe1b0e8f198afb00180248721fcae7a4f1dac8f8d91200e7aac5a4245e4f0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e042cfbee1f7a7607fee0373e1ec977d20a79d3d7bef489ab57944cf026a8c0 0.600000000000 1446069 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": 985858, "vin": [ { "gen": { "height": 985848 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e042cfbee1f7a7607fee0373e1ec977d20a79d3d7bef489ab57944cf026a8c0" } } ], "extra": [ 1, 255, 15, 190, 27, 14, 143, 25, 138, 251, 0, 24, 2, 72, 114, 31, 202, 231, 164, 241, 218, 200, 248, 217, 18, 0, 231, 170, 197, 164, 36, 94, 79, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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