Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d6eea1e6cccfc007f58f3315bda31e47b80f06968aca0106773b027558b50bff

Tx prefix hash: 61ca5757e1f89ea7548f827564efaf16cf7f5f76af09d85c4a49a7c85d1b025f
Tx public key: 3e00c21c87c68e16e8bfbcd06836f9cac826230e8ed90684e9f8bf267edfee51
Timestamp: 1741374626 Timestamp [UCT]: 2025-03-07 19:10:26 Age [y:d:h:m:s]: 00:258:19:31:12
Block: 1234308 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 182705 RingCT/type: yes/0
Extra: 013e00c21c87c68e16e8bfbcd06836f9cac826230e8ed90684e9f8bf267edfee510211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8be1d061673cf774a9b11737e5610824649d58573d4b2363a9583e4c7a6d8dcb 0.600000000000 1721235 of 15

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": 1234318, "vin": [ { "gen": { "height": 1234308 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8be1d061673cf774a9b11737e5610824649d58573d4b2363a9583e4c7a6d8dcb" } } ], "extra": [ 1, 62, 0, 194, 28, 135, 198, 142, 22, 232, 191, 188, 208, 104, 54, 249, 202, 200, 38, 35, 14, 142, 217, 6, 132, 233, 248, 191, 38, 126, 223, 238, 81, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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