Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 03ae5c2c3790bbf7c8cc24a336d8074be73ee5acc56b25791eb7dd55a008ebdc

Tx prefix hash: cbbd296c79f3bde7c08069789590cf9d529b15232091026f1ad80a2eff96ae99
Tx public key: bc88276b2b685ada217d96f9964b4a625aed901b77bf298d181db1d91f74226e
Timestamp: 1736448385 Timestamp [UCT]: 2025-01-09 18:46:25 Age [y:d:h:m:s]: 00:115:12:12:39
Block: 1193778 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 82360 RingCT/type: yes/0
Extra: 01bc88276b2b685ada217d96f9964b4a625aed901b77bf298d181db1d91f74226e0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 39369d2db96221d75becee83a4e0abdc3d4f6af2cbdbff733559e25515f5e9dc 0.600000000000 1680343 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": 1193788, "vin": [ { "gen": { "height": 1193778 } } ], "vout": [ { "amount": 600000000, "target": { "key": "39369d2db96221d75becee83a4e0abdc3d4f6af2cbdbff733559e25515f5e9dc" } } ], "extra": [ 1, 188, 136, 39, 107, 43, 104, 90, 218, 33, 125, 150, 249, 150, 75, 74, 98, 90, 237, 144, 27, 119, 191, 41, 141, 24, 29, 177, 217, 31, 116, 34, 110, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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