Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a2456f65d70b83e962bc53cf1e98a66cf59e795273b1a916d942ce458cb28a8

Tx prefix hash: bb575763f84f0d914d7c0894c664e80445e4fa5d9f748566768e927472719294
Tx public key: ea206e4d34dc2ef4425d5636df464dc6e2d2c4dd1121a33648251df6cbbd7896
Timestamp: 1638307264 Timestamp [UCT]: 2021-11-30 21:21:04 Age [y:d:h:m:s]: 03:104:18:32:28
Block: 385640 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 853589 RingCT/type: yes/0
Extra: 01ea206e4d34dc2ef4425d5636df464dc6e2d2c4dd1121a33648251df6cbbd7896021100000015d6e4826b000000000000000000

1 output(s) for total of 32.377926792000 dcy

stealth address amount amount idx
00: 9fd8a8f062a540e1b7fbc4e6c676b01840d873687e0aa77a3949f24e0598bd98 32.377926792000 778189 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": 385650, "vin": [ { "gen": { "height": 385640 } } ], "vout": [ { "amount": 32377926792, "target": { "key": "9fd8a8f062a540e1b7fbc4e6c676b01840d873687e0aa77a3949f24e0598bd98" } } ], "extra": [ 1, 234, 32, 110, 77, 52, 220, 46, 244, 66, 93, 86, 54, 223, 70, 77, 198, 226, 210, 196, 221, 17, 33, 163, 54, 72, 37, 29, 246, 203, 189, 120, 150, 2, 17, 0, 0, 0, 21, 214, 228, 130, 107, 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