Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 33bc4e8237c90d19dabf58165b1fa54a20b9624732324a085c3168d84484207f

Tx prefix hash: a5d48bc158d5b1d9568e6e528328ab4a1bcd2182667d16073e00e31124a7fc7d
Tx public key: 5e685f3a63eeb7ad8f9d31e4c133038cfa1bbff0579274a89175ce6b7c9fef10
Timestamp: 1638161637 Timestamp [UCT]: 2021-11-29 04:53:57 Age [y:d:h:m:s]: 03:337:07:32:37
Block: 384438 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1017489 RingCT/type: yes/0
Extra: 015e685f3a63eeb7ad8f9d31e4c133038cfa1bbff0579274a89175ce6b7c9fef1002110000000ae9564d6f000000000000000000

1 output(s) for total of 32.673652998000 dcy

stealth address amount amount idx
00: 535241042ba869ebbe4d273e6c82593fa12c4365e575e9ad69708ecb58213c4b 32.673652998000 775937 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": 384448, "vin": [ { "gen": { "height": 384438 } } ], "vout": [ { "amount": 32673652998, "target": { "key": "535241042ba869ebbe4d273e6c82593fa12c4365e575e9ad69708ecb58213c4b" } } ], "extra": [ 1, 94, 104, 95, 58, 99, 238, 183, 173, 143, 157, 49, 228, 193, 51, 3, 140, 250, 27, 191, 240, 87, 146, 116, 168, 145, 117, 206, 107, 124, 159, 239, 16, 2, 17, 0, 0, 0, 10, 233, 86, 77, 111, 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