Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2595b0f0cbe663da79498a9ed896b5e2055e49e5c5e033ff41d18deb510053ea

Tx prefix hash: 7c24e68ba7e4eb55fd602b0af864174f2e1f1b73e00a642f9a61c10031ac7e1f
Tx public key: 471e3922dc5af7dbb368b9892f93076539cdce93168050079b9e95ebb393a2af
Timestamp: 1710413548 Timestamp [UCT]: 2024-03-14 10:52:28 Age [y:d:h:m:s]: 01:240:01:35:26
Block: 978100 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 430268 RingCT/type: yes/0
Extra: 01471e3922dc5af7dbb368b9892f93076539cdce93168050079b9e95ebb393a2af021100000002679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6ba3acb3b1eeccb8191c7ea18d922ff153166275ec6eee6ac09cd936ce4aa2aa 0.600000000000 1438117 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": 978110, "vin": [ { "gen": { "height": 978100 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6ba3acb3b1eeccb8191c7ea18d922ff153166275ec6eee6ac09cd936ce4aa2aa" } } ], "extra": [ 1, 71, 30, 57, 34, 220, 90, 247, 219, 179, 104, 185, 137, 47, 147, 7, 101, 57, 205, 206, 147, 22, 128, 80, 7, 155, 158, 149, 235, 179, 147, 162, 175, 2, 17, 0, 0, 0, 2, 103, 154, 138, 129, 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