Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 529a02d75797644cd5c8c8fa281c002c2176c5336571cb06c509b8a1a6a2715e

Tx prefix hash: ebfd3394e88d27d516a5dc6e6bd9479d696af9cccd8d74f4940d21ca6409353d
Tx public key: 54d8d0f8c4c4156793d5ca03d78ec31dffa5212dd5300df61deb5b07e3ca8f85
Timestamp: 1709715427 Timestamp [UCT]: 2024-03-06 08:57:07 Age [y:d:h:m:s]: 01:251:00:18:06
Block: 972306 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 438104 RingCT/type: yes/0
Extra: 0154d8d0f8c4c4156793d5ca03d78ec31dffa5212dd5300df61deb5b07e3ca8f850211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d6656ef14babdd44405a052a29d6585f4606f7fa9349a8b0a22cce061ac0dd9e 0.600000000000 1432215 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": 972316, "vin": [ { "gen": { "height": 972306 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d6656ef14babdd44405a052a29d6585f4606f7fa9349a8b0a22cce061ac0dd9e" } } ], "extra": [ 1, 84, 216, 208, 248, 196, 196, 21, 103, 147, 213, 202, 3, 215, 142, 195, 29, 255, 165, 33, 45, 213, 48, 13, 246, 29, 235, 91, 7, 227, 202, 143, 133, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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