Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d9b92a41c9f96bbf7a8709af1193e2feadfa3cd7ca05ce3ccc28fab827bb97c

Tx prefix hash: ca4c55f0bb1ec4a8f572da3d2b3e70b92bb54bf6d26cba62b460bba094c026c3
Tx public key: 092448ec32b7f38f040c7299ee600678c266ce5581c8eacd6b7b61873c93410e
Timestamp: 1681238337 Timestamp [UCT]: 2023-04-11 18:38:57 Age [y:d:h:m:s]: 01:363:10:34:10
Block: 736440 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 521038 RingCT/type: yes/0
Extra: 01092448ec32b7f38f040c7299ee600678c266ce5581c8eacd6b7b61873c93410e0211000000015029cbac000000000000000000

1 output(s) for total of 2.227762003000 dcy

stealth address amount amount idx
00: 81672e7f4ec10c35826143ef0bb067361c060c089ff99fedad4fb00ff10f18f1 2.227762003000 1182873 of 0

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": 736450, "vin": [ { "gen": { "height": 736440 } } ], "vout": [ { "amount": 2227762003, "target": { "key": "81672e7f4ec10c35826143ef0bb067361c060c089ff99fedad4fb00ff10f18f1" } } ], "extra": [ 1, 9, 36, 72, 236, 50, 183, 243, 143, 4, 12, 114, 153, 238, 96, 6, 120, 194, 102, 206, 85, 129, 200, 234, 205, 107, 123, 97, 135, 60, 147, 65, 14, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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