Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a15d33d319e9eec12aed4fbf273e4b89b2dad030fa5a1f1cdd476784954bff52

Tx prefix hash: 675ee5f3bbb4169678da876526a9d6658a852bc2d1692e8fb830b7f14692639e
Tx public key: d6e888b730dfd916bfd4849a5336d3db1e797b6383d102397468059666c0339f
Timestamp: 1764155055 Timestamp [UCT]: 2025-11-26 11:04:15 Age [y:d:h:m:s]: 00:000:01:27:13
Block: 1420494 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 42 RingCT/type: yes/0
Extra: 01d6e888b730dfd916bfd4849a5336d3db1e797b6383d102397468059666c0339f0211000000014e7bfc09000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0514a931aa241a6bb0552460e4ee1e7a2066cb9e9a93ffcb9520b117c62d8d96 0.600000000000 1909037 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": 1420504, "vin": [ { "gen": { "height": 1420494 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0514a931aa241a6bb0552460e4ee1e7a2066cb9e9a93ffcb9520b117c62d8d96" } } ], "extra": [ 1, 214, 232, 136, 183, 48, 223, 217, 22, 191, 212, 132, 154, 83, 54, 211, 219, 30, 121, 123, 99, 131, 209, 2, 57, 116, 104, 5, 150, 102, 192, 51, 159, 2, 17, 0, 0, 0, 1, 78, 123, 252, 9, 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