Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9e56017b4c49199751659ab629d123b4cb4e9f4d715c5439dd0b4768689fa3b7

Tx prefix hash: a407abae75092b8bc23a9fc8a06da5cce8e750cd3d0b62c3244768871a5efaf7
Tx public key: 2e45e811cbbb03a8363adb65e149515af3618a6918de8af3cea2134720cb21e6
Timestamp: 1763197123 Timestamp [UCT]: 2025-11-15 08:58:43 Age [y:d:h:m:s]: 00:054:01:48:09
Block: 1412554 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 38724 RingCT/type: yes/0
Extra: 012e45e811cbbb03a8363adb65e149515af3618a6918de8af3cea2134720cb21e6021100000004e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c1a2797363ec1fdec5e731b1e0f550d42f0dac755f7796d6c5bdbf9b105b2c5b 0.600000000000 1901025 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": 1412564, "vin": [ { "gen": { "height": 1412554 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c1a2797363ec1fdec5e731b1e0f550d42f0dac755f7796d6c5bdbf9b105b2c5b" } } ], "extra": [ 1, 46, 69, 232, 17, 203, 187, 3, 168, 54, 58, 219, 101, 225, 73, 81, 90, 243, 97, 138, 105, 24, 222, 138, 243, 206, 162, 19, 71, 32, 203, 33, 230, 2, 17, 0, 0, 0, 4, 228, 220, 144, 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