Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 44f12243a4ea823bd4844c0faaec3ca32aa86644c830fbeb5ec23da31ab72a78

Tx prefix hash: 57c22f4296930cf6c471d2e0b54edd929aa6c3c151c38501695f948f62c835e3
Tx public key: 1a15c1d87fdf3ccce4f727ee51882aac957892bbd1a18e67f5d561967254bd3f
Timestamp: 1735097613 Timestamp [UCT]: 2024-12-25 03:33:33 Age [y:d:h:m:s]: 00:105:18:39:24
Block: 1182610 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 75377 RingCT/type: yes/0
Extra: 011a15c1d87fdf3ccce4f727ee51882aac957892bbd1a18e67f5d561967254bd3f0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fb00d5db478013b406b1f57c8e35708335c93eff8cfc57f74a323ef97fe059cc 0.600000000000 1669045 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": 1182620, "vin": [ { "gen": { "height": 1182610 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fb00d5db478013b406b1f57c8e35708335c93eff8cfc57f74a323ef97fe059cc" } } ], "extra": [ 1, 26, 21, 193, 216, 127, 223, 60, 204, 228, 247, 39, 238, 81, 136, 42, 172, 149, 120, 146, 187, 209, 161, 142, 103, 245, 213, 97, 150, 114, 84, 189, 63, 2, 17, 0, 0, 0, 3, 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