Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f5a913ca04411b83c82bae94224513500065994526b9b4ba7be84f6b389dfa16

Tx prefix hash: 2dfb45460e71e6df88fd9883e71817d6fcee8e4e24edb9319f9b5669549dacd6
Tx public key: 0b5786c9b870097ba72aa592052686e0c3f994eb4cebb38e6dff40d684220120
Timestamp: 1761388064 Timestamp [UCT]: 2025-10-25 10:27:44 Age [y:d:h:m:s]: 00:059:17:41:53
Block: 1397576 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 42756 RingCT/type: yes/0
Extra: 010b5786c9b870097ba72aa592052686e0c3f994eb4cebb38e6dff40d684220120021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 240377c7d333a64d4b1bfe8bcd7b6351b4db9ee8297910c4f4c9b7b0e64c5bc4 0.600000000000 1885867 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": 1397586, "vin": [ { "gen": { "height": 1397576 } } ], "vout": [ { "amount": 600000000, "target": { "key": "240377c7d333a64d4b1bfe8bcd7b6351b4db9ee8297910c4f4c9b7b0e64c5bc4" } } ], "extra": [ 1, 11, 87, 134, 201, 184, 112, 9, 123, 167, 42, 165, 146, 5, 38, 134, 224, 195, 249, 148, 235, 76, 235, 179, 142, 109, 255, 64, 214, 132, 34, 1, 32, 2, 17, 0, 0, 0, 1, 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