Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a1f3bab6b152ea1c2e6b21b978f59bb47da0c9495bd11ecf06f36532fff5fff6

Tx prefix hash: c956bede5a36a929176d919db18568d26b4bb6a8b17d17986bb49c068bf8892a
Tx public key: 71717c37c0fb66d4fc9ebba70851134806f74d768ce486af2836c094ad37e65b
Timestamp: 1713732545 Timestamp [UCT]: 2024-04-21 20:49:05 Age [y:d:h:m:s]: 00:254:16:50:18
Block: 1005585 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 182326 RingCT/type: yes/0
Extra: 0171717c37c0fb66d4fc9ebba70851134806f74d768ce486af2836c094ad37e65b0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bce02d3d4c1c5a4e998526655dea3a013dd59d01c417351c4f87ea71dfaa6e5f 0.600000000000 1466323 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": 1005595, "vin": [ { "gen": { "height": 1005585 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bce02d3d4c1c5a4e998526655dea3a013dd59d01c417351c4f87ea71dfaa6e5f" } } ], "extra": [ 1, 113, 113, 124, 55, 192, 251, 102, 212, 252, 158, 187, 167, 8, 81, 19, 72, 6, 247, 77, 118, 140, 228, 134, 175, 40, 54, 192, 148, 173, 55, 230, 91, 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