Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9e66bd2ddfd0203cfea50aa1ac44512bf0e7c6f91369a75a70188ecae321e3c2

Tx prefix hash: 35e95f64c5eb9c298e0c9b2776d89134902b91f07d4bbe983c985850f9b08cde
Tx public key: 8defa18793351e0f4c923efccbf3a157c6013a298c83f6bcbf93ed3dd8c7b738
Timestamp: 1707191786 Timestamp [UCT]: 2024-02-06 03:56:26 Age [y:d:h:m:s]: 01:055:19:52:12
Block: 951356 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 300952 RingCT/type: yes/0
Extra: 018defa18793351e0f4c923efccbf3a157c6013a298c83f6bcbf93ed3dd8c7b73802110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2de668dbf57e8b7f39e0b3935f8a7e093ce33a73ce344c15a5c8ea1c5424a000 0.600000000000 1410110 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": 951366, "vin": [ { "gen": { "height": 951356 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2de668dbf57e8b7f39e0b3935f8a7e093ce33a73ce344c15a5c8ea1c5424a000" } } ], "extra": [ 1, 141, 239, 161, 135, 147, 53, 30, 15, 76, 146, 62, 252, 203, 243, 161, 87, 198, 1, 58, 41, 140, 131, 246, 188, 191, 147, 237, 61, 216, 199, 183, 56, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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