Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8bf7b8a15f607191d0e847815eb72b3ac0560f69d5fb7fa8f5b9ac578577661b

Tx prefix hash: 7e5d019230af4fbfc2ede89596e822936eaad2f038220a7a49b30a0a1b5426da
Tx public key: d47074ec47ee5df8448fe74364f753419768cf072f37a3b1bf03184a7621351c
Timestamp: 1638971670 Timestamp [UCT]: 2021-12-08 13:54:30 Age [y:d:h:m:s]: 03:328:06:03:54
Block: 391109 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1011042 RingCT/type: yes/0
Extra: 01d47074ec47ee5df8448fe74364f753419768cf072f37a3b1bf03184a7621351c021100000010379224c2000000000000000000

1 output(s) for total of 31.052308373000 dcy

stealth address amount amount idx
00: 9d1c619892a0ba3cbc5348ddd2f144562f3ee44ff419398ef2593cbf4eb7e083 31.052308373000 787300 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": 391119, "vin": [ { "gen": { "height": 391109 } } ], "vout": [ { "amount": 31052308373, "target": { "key": "9d1c619892a0ba3cbc5348ddd2f144562f3ee44ff419398ef2593cbf4eb7e083" } } ], "extra": [ 1, 212, 112, 116, 236, 71, 238, 93, 248, 68, 143, 231, 67, 100, 247, 83, 65, 151, 104, 207, 7, 47, 55, 163, 177, 191, 3, 24, 74, 118, 33, 53, 28, 2, 17, 0, 0, 0, 16, 55, 146, 36, 194, 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