Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc7344945a8aa1edd827d71ae904831f51c0f3a06b71ae797b8250d0eeb82c21

Tx prefix hash: ee5dd04ff33f26348917de3388d487b6bcc1672e4edb362bc5e9403f1b8c0116
Tx public key: 6036adf3a4873e1dedeb39dcb68d893788dfd46193f3524cdef44f22ace8ce0c
Timestamp: 1580694460 Timestamp [UCT]: 2020-02-03 01:47:40 Age [y:d:h:m:s]: 04:277:21:39:18
Block: 57419 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1089977 RingCT/type: yes/0
Extra: 016036adf3a4873e1dedeb39dcb68d893788dfd46193f3524cdef44f22ace8ce0c02110000003d391a8d0e000000000000000000

1 output(s) for total of 396.048013552000 dcy

stealth address amount amount idx
00: 0f523020f417f4dab7bffc6f7a9149424b1f10e1cc42d8c671c5e1dbd452c033 396.048013552000 106139 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": 57429, "vin": [ { "gen": { "height": 57419 } } ], "vout": [ { "amount": 396048013552, "target": { "key": "0f523020f417f4dab7bffc6f7a9149424b1f10e1cc42d8c671c5e1dbd452c033" } } ], "extra": [ 1, 96, 54, 173, 243, 164, 135, 62, 29, 237, 235, 57, 220, 182, 141, 137, 55, 136, 223, 212, 97, 147, 243, 82, 76, 222, 244, 79, 34, 172, 232, 206, 12, 2, 17, 0, 0, 0, 61, 57, 26, 141, 14, 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