Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dafe880e740940fea278f2fafe1b66f433dacd5833695d5a7bec2e8ada5941d9

Tx prefix hash: 17da8fc1a19a6f4e5bfa30910575909962b03c5036274b2bcc243e9ba1119bf4
Tx public key: d1bfb6f34e1789f295802d0a611e52a1ec532582fa2be9e071837c8537a259b0
Timestamp: 1749502861 Timestamp [UCT]: 2025-06-09 21:01:01 Age [y:d:h:m:s]: 00:157:02:58:34
Block: 1301594 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109984 RingCT/type: yes/0
Extra: 01d1bfb6f34e1789f295802d0a611e52a1ec532582fa2be9e071837c8537a259b00211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 19a85dbdecc94f97d86297a0ab2503ecbf6f8beecc3c6eeb3d3c6929715c2d36 0.600000000000 1789155 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": 1301604, "vin": [ { "gen": { "height": 1301594 } } ], "vout": [ { "amount": 600000000, "target": { "key": "19a85dbdecc94f97d86297a0ab2503ecbf6f8beecc3c6eeb3d3c6929715c2d36" } } ], "extra": [ 1, 209, 191, 182, 243, 78, 23, 137, 242, 149, 128, 45, 10, 97, 30, 82, 161, 236, 83, 37, 130, 250, 43, 233, 224, 113, 131, 124, 133, 55, 162, 89, 176, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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