Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2a8f2fd4c697e24d48178bddb969d2f37f48a2c1b6bcaaf6ed51b6f54d843de9

Tx prefix hash: c845b4400f1bbf2bdf9b8a36ae29e4543c0f934c62ce39cf830db6cd74ea5136
Tx public key: 3445288cf2e85fdb26efd18ca75c0838145afed896a206441b4574e529f3cfc6
Timestamp: 1722974466 Timestamp [UCT]: 2024-08-06 20:01:06 Age [y:d:h:m:s]: 00:247:22:54:29
Block: 1082214 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177111 RingCT/type: yes/0
Extra: 013445288cf2e85fdb26efd18ca75c0838145afed896a206441b4574e529f3cfc602110000000b91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e25213c55be2ff529384ccd85c00a9249a54f0571d2e0682fe0b1a67f701acf9 0.600000000000 1556039 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": 1082224, "vin": [ { "gen": { "height": 1082214 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e25213c55be2ff529384ccd85c00a9249a54f0571d2e0682fe0b1a67f701acf9" } } ], "extra": [ 1, 52, 69, 40, 140, 242, 232, 95, 219, 38, 239, 209, 140, 167, 92, 8, 56, 20, 90, 254, 216, 150, 162, 6, 68, 27, 69, 116, 229, 41, 243, 207, 198, 2, 17, 0, 0, 0, 11, 145, 225, 60, 4, 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