Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e9ff6c714a37fa4ea7e53886a1ea53716ff652297f97fcd04d2d0fa41cbb8f4

Tx prefix hash: 3aabfcb2ebd0852b80aeb3dbb3bdbb9db350838d40db43699aa338fc9c446a61
Tx public key: 3d609d6784dbe11f9f653fae2a492b8ee84a446930ecd0e7b9ce0c67d046ba3e
Timestamp: 1737065169 Timestamp [UCT]: 2025-01-16 22:06:09 Age [y:d:h:m:s]: 00:154:00:05:40
Block: 1198888 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109746 RingCT/type: yes/0
Extra: 013d609d6784dbe11f9f653fae2a492b8ee84a446930ecd0e7b9ce0c67d046ba3e02110000000d007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e5b0b71069e03688ee5fc083c86a065e175950a7fa63876bf2de48ff1546fcab 0.600000000000 1685515 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": 1198898, "vin": [ { "gen": { "height": 1198888 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e5b0b71069e03688ee5fc083c86a065e175950a7fa63876bf2de48ff1546fcab" } } ], "extra": [ 1, 61, 96, 157, 103, 132, 219, 225, 31, 159, 101, 63, 174, 42, 73, 43, 142, 232, 74, 68, 105, 48, 236, 208, 231, 185, 206, 12, 103, 208, 70, 186, 62, 2, 17, 0, 0, 0, 13, 0, 127, 151, 138, 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