Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb6ea04446229ccac0eb1a529cbe9192671e64027a970a72ccc24a68c70d3335

Tx prefix hash: 221ca94de8c98b175e719baedf3147c98b0075cf4b203a2f3182cbe4d496177b
Tx public key: 185a0216d23f4981aa98f2a069757b2ebffb45dd7e8840afc3affb9ef845a800
Timestamp: 1632401551 Timestamp [UCT]: 2021-09-23 12:52:31 Age [y:d:h:m:s]: 03:225:08:48:42
Block: 339463 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 937101 RingCT/type: yes/0
Extra: 01185a0216d23f4981aa98f2a069757b2ebffb45dd7e8840afc3affb9ef845a800021100000039f29d7abf000000000000000000

1 output(s) for total of 46.048829569000 dcy

stealth address amount amount idx
00: 5e0c57270eeaac205530bedd5480abc2e35b542025e7a65fb5f3c73e8bd3b867 46.048829569000 698150 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": 339473, "vin": [ { "gen": { "height": 339463 } } ], "vout": [ { "amount": 46048829569, "target": { "key": "5e0c57270eeaac205530bedd5480abc2e35b542025e7a65fb5f3c73e8bd3b867" } } ], "extra": [ 1, 24, 90, 2, 22, 210, 63, 73, 129, 170, 152, 242, 160, 105, 117, 123, 46, 191, 251, 69, 221, 126, 136, 64, 175, 195, 175, 251, 158, 248, 69, 168, 0, 2, 17, 0, 0, 0, 57, 242, 157, 122, 191, 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