Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e0e0cfdd86dbeb491501acaa6ca37795d43286ebb1a9d4ddaec6fce04524c65a

Tx prefix hash: 9834b9958c888648ad44881752d60eb4ce0c5d0edb44a70353327fccc6bc9e03
Tx public key: 9536814b54dfb9df49247fc406e1e9887248a33e05b4be2e554c8b41a986a33d
Timestamp: 1648674136 Timestamp [UCT]: 2022-03-30 21:02:16 Age [y:d:h:m:s]: 03:215:05:49:59
Block: 469828 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 931813 RingCT/type: yes/0
Extra: 019536814b54dfb9df49247fc406e1e9887248a33e05b4be2e554c8b41a986a33d0211000000025eb576c5000000000000000000

1 output(s) for total of 17.031976564000 dcy

stealth address amount amount idx
00: 9bc2327a5c8dfe02bdd7b46ede5c750b33b3d590d54e4b9f9ef6dcc200f41c7c 17.031976564000 888848 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": 469838, "vin": [ { "gen": { "height": 469828 } } ], "vout": [ { "amount": 17031976564, "target": { "key": "9bc2327a5c8dfe02bdd7b46ede5c750b33b3d590d54e4b9f9ef6dcc200f41c7c" } } ], "extra": [ 1, 149, 54, 129, 75, 84, 223, 185, 223, 73, 36, 127, 196, 6, 225, 233, 136, 114, 72, 163, 62, 5, 180, 190, 46, 85, 76, 139, 65, 169, 134, 163, 61, 2, 17, 0, 0, 0, 2, 94, 181, 118, 197, 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