Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bbfa39499a3adf81e7aaee9389bbcaaaa0f9fefa7269d8c11ab147389ce4208a

Tx prefix hash: 57d87601f3bf35ff5754a389060df3f870a2199969b3fb91feb0e4204b12f390
Tx public key: cdb3e565344f411f5a3fd68080b5e52ac503dce03ffd3ff7fa303857a0ecbfc1
Timestamp: 1578239497 Timestamp [UCT]: 2020-01-05 15:51:37 Age [y:d:h:m:s]: 04:305:22:59:51
Block: 39304 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1107845 RingCT/type: yes/0
Extra: 01cdb3e565344f411f5a3fd68080b5e52ac503dce03ffd3ff7fa303857a0ecbfc10211000000492264afe6000000000000000000

1 output(s) for total of 454.767683457000 dcy

stealth address amount amount idx
00: cd37793cfed8b1ea029483b7c2a5be010319bbad0a65cd8ea6227a3d577e583f 454.767683457000 67667 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": 39314, "vin": [ { "gen": { "height": 39304 } } ], "vout": [ { "amount": 454767683457, "target": { "key": "cd37793cfed8b1ea029483b7c2a5be010319bbad0a65cd8ea6227a3d577e583f" } } ], "extra": [ 1, 205, 179, 229, 101, 52, 79, 65, 31, 90, 63, 214, 128, 128, 181, 229, 42, 197, 3, 220, 224, 63, 253, 63, 247, 250, 48, 56, 87, 160, 236, 191, 193, 2, 17, 0, 0, 0, 73, 34, 100, 175, 230, 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