Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 84d924737f3719ad8998d95f2aaf1aaa31c70d7866eb74efa88c2b54f12358e5

Tx prefix hash: c8e3a3c80e363879fe97b47ad05dcb1ce5e025ed62e9b4b95ea237b929cb5afd
Tx public key: 1e4395253f3029e3301ba742dc4c4bdcb38eb1eee960a59addad1ca2111f40af
Timestamp: 1634841360 Timestamp [UCT]: 2021-10-21 18:36:00 Age [y:d:h:m:s]: 03:189:15:21:26
Block: 357605 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 913619 RingCT/type: yes/0
Extra: 011e4395253f3029e3301ba742dc4c4bdcb38eb1eee960a59addad1ca2111f40af02110000000af60c5d7e000000000000000000

1 output(s) for total of 40.096512334000 dcy

stealth address amount amount idx
00: c454e1b9dd422e21a480c653758cd724f8eb1aaab59ca268f89211064933bcbf 40.096512334000 729121 of 0

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": 357615, "vin": [ { "gen": { "height": 357605 } } ], "vout": [ { "amount": 40096512334, "target": { "key": "c454e1b9dd422e21a480c653758cd724f8eb1aaab59ca268f89211064933bcbf" } } ], "extra": [ 1, 30, 67, 149, 37, 63, 48, 41, 227, 48, 27, 167, 66, 220, 76, 75, 220, 179, 142, 177, 238, 233, 96, 165, 154, 221, 173, 28, 162, 17, 31, 64, 175, 2, 17, 0, 0, 0, 10, 246, 12, 93, 126, 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