Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 99812d558b905fbde9d2ee6ec76f89812b362311ad8961c2a0e952c7894b78ae

Tx prefix hash: 486f9c34d650cce5b74a8b0b9fb9adb9df72e12b059ef5e47b0aa350375a6159
Tx public key: d2aae5d0101783cf4a72aee1c20be115862712f9b8834f058c56ea6ea8c01560
Timestamp: 1761925982 Timestamp [UCT]: 2025-10-31 15:53:02 Age [y:d:h:m:s]: 00:053:02:04:42
Block: 1402023 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 38000 RingCT/type: yes/0
Extra: 01d2aae5d0101783cf4a72aee1c20be115862712f9b8834f058c56ea6ea8c0156002110000000325a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d6ae3fd909f094352fc28fef2268ee8d8cd323ee80aa821c735ec509ae9d5b8b 0.600000000000 1890342 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": 1402033, "vin": [ { "gen": { "height": 1402023 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d6ae3fd909f094352fc28fef2268ee8d8cd323ee80aa821c735ec509ae9d5b8b" } } ], "extra": [ 1, 210, 170, 229, 208, 16, 23, 131, 207, 74, 114, 174, 225, 194, 11, 225, 21, 134, 39, 18, 249, 184, 131, 79, 5, 140, 86, 234, 110, 168, 192, 21, 96, 2, 17, 0, 0, 0, 3, 37, 163, 90, 15, 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