Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d9e268b153e82546521d3c9e4a138aaf906aa80010d26def23772251f431d84e

Tx prefix hash: 83ffe5d25802b492e2bd41f09324fb4607aee5ccee5d7d22584aace51b57409f
Tx public key: e44904c64b3f4d7c7c68d5c8012ab879d8dbe6df7d3afa01d33db77d117c6026
Timestamp: 1737259423 Timestamp [UCT]: 2025-01-19 04:03:43 Age [y:d:h:m:s]: 00:332:10:48:50
Block: 1200466 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 235176 RingCT/type: yes/0
Extra: 01e44904c64b3f4d7c7c68d5c8012ab879d8dbe6df7d3afa01d33db77d117c602602110000000d007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a96bda1ea4e08fc455ecbe719a3d0e1ba4cc56daad078eb74ccec468f0339af1 0.600000000000 1687109 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": 1200476, "vin": [ { "gen": { "height": 1200466 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a96bda1ea4e08fc455ecbe719a3d0e1ba4cc56daad078eb74ccec468f0339af1" } } ], "extra": [ 1, 228, 73, 4, 198, 75, 63, 77, 124, 124, 104, 213, 200, 1, 42, 184, 121, 216, 219, 230, 223, 125, 58, 250, 1, 211, 61, 183, 125, 17, 124, 96, 38, 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