Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c7c392445a29336f3964ded7b601ccba4e5af449c0ec6d155146b2b1a1a630cc

Tx prefix hash: 18dc77984b25d8b69d3ea6fe499094a76fb118fdc6c8e7c87009191fd036c82b
Tx public key: 3932b229cf16522f55e454963a6ae12c980aa3bb2d910341e0865241117cbf83
Timestamp: 1737390334 Timestamp [UCT]: 2025-01-20 16:25:34 Age [y:d:h:m:s]: 00:297:14:45:12
Block: 1201532 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210259 RingCT/type: yes/0
Extra: 013932b229cf16522f55e454963a6ae12c980aa3bb2d910341e0865241117cbf830211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8f45323157a0bea57bd2ebf4a93d6c4f533c0d6f8ac1365ca05acfd13e45bde6 0.600000000000 1688185 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": 1201542, "vin": [ { "gen": { "height": 1201532 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8f45323157a0bea57bd2ebf4a93d6c4f533c0d6f8ac1365ca05acfd13e45bde6" } } ], "extra": [ 1, 57, 50, 178, 41, 207, 22, 82, 47, 85, 228, 84, 150, 58, 106, 225, 44, 152, 10, 163, 187, 45, 145, 3, 65, 224, 134, 82, 65, 17, 124, 191, 131, 2, 17, 0, 0, 0, 5, 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