Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 416db6e6806ef5fc4a22625d86c82e6dcf70c0b40365b947db9f2267bb59632b

Tx prefix hash: f328fe8fa1fca37d2e176037741148a1fe9bb80f0cca76cc3d8bd0141c28143b
Tx public key: 7436c753bd6e8e8e25ee760542e4f36e18d66054f9fc2cecfbc8c1c57f563f9e
Timestamp: 1717800817 Timestamp [UCT]: 2024-06-07 22:53:37 Age [y:d:h:m:s]: 00:267:21:15:31
Block: 1039322 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 191428 RingCT/type: yes/0
Extra: 017436c753bd6e8e8e25ee760542e4f36e18d66054f9fc2cecfbc8c1c57f563f9e02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9ad982adc579f30c95dbb206449b3a954626373caf6ee78c6f0bc3813d5a1ab9 0.600000000000 1507955 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": 1039332, "vin": [ { "gen": { "height": 1039322 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9ad982adc579f30c95dbb206449b3a954626373caf6ee78c6f0bc3813d5a1ab9" } } ], "extra": [ 1, 116, 54, 199, 83, 189, 110, 142, 142, 37, 238, 118, 5, 66, 228, 243, 110, 24, 214, 96, 84, 249, 252, 44, 236, 251, 200, 193, 197, 127, 86, 63, 158, 2, 17, 0, 0, 0, 1, 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