Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d5bbb52374854a1f8bc65d2ea7ab69b965ab2ef7587541369b534c646e0704d5

Tx prefix hash: 263dd487296ba53e88a0f62791d466e140f0bf7c5c791c114998eca9f900b1fd
Tx public key: e4bf4ec509e72a6c2e6042cea55fb305c05fbcae636d9b3a4baad1ea3a25b2ca
Timestamp: 1740996095 Timestamp [UCT]: 2025-03-03 10:01:35 Age [y:d:h:m:s]: 00:256:15:14:30
Block: 1231161 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181164 RingCT/type: yes/0
Extra: 01e4bf4ec509e72a6c2e6042cea55fb305c05fbcae636d9b3a4baad1ea3a25b2ca0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a1877a687fe67ddc10c5b4ab13ca3e7ee24cc510227ba996cbd59e38f0521e34 0.600000000000 1718066 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": 1231171, "vin": [ { "gen": { "height": 1231161 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a1877a687fe67ddc10c5b4ab13ca3e7ee24cc510227ba996cbd59e38f0521e34" } } ], "extra": [ 1, 228, 191, 78, 197, 9, 231, 42, 108, 46, 96, 66, 206, 165, 95, 179, 5, 192, 95, 188, 174, 99, 109, 155, 58, 75, 170, 209, 234, 58, 37, 178, 202, 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