Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5aa3d35d8347316938b8a37272253b71de97cdcc7d1b59eaff3d7bf6d2eacb67

Tx prefix hash: 7dc44d08a3ef15c42b808764c7f8aee658bdbc375c2bd59ebf488f7c39f11ceb
Tx public key: 14ca26c87654d9f3e12a2ee535af4104522c4e4198309a7eec1966133a76e5be
Timestamp: 1744335534 Timestamp [UCT]: 2025-04-11 01:38:54 Age [y:d:h:m:s]: 00:033:15:02:30
Block: 1258808 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 24064 RingCT/type: yes/0
Extra: 0114ca26c87654d9f3e12a2ee535af4104522c4e4198309a7eec1966133a76e5be02110000000bdbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c9c3675e250e95e0c73d1e836f28aa93eb987d4aef3c7aea15aecc9df7a0c529 0.600000000000 1745945 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": 1258818, "vin": [ { "gen": { "height": 1258808 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c9c3675e250e95e0c73d1e836f28aa93eb987d4aef3c7aea15aecc9df7a0c529" } } ], "extra": [ 1, 20, 202, 38, 200, 118, 84, 217, 243, 225, 42, 46, 229, 53, 175, 65, 4, 82, 44, 78, 65, 152, 48, 154, 126, 236, 25, 102, 19, 58, 118, 229, 190, 2, 17, 0, 0, 0, 11, 219, 181, 113, 193, 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