Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4a2c69c96c8330f8af552c4ffb38515e4c902db35040cc00a102cce4e3082e5

Tx prefix hash: c3e19503c2902ded0bbd0ca7bf47c96dc5c853a514bc416225e03a0b2b9dfc2f
Tx public key: cd5ce3c3798741e7d555fda968ef3a545d10b45949b31ede6eeea0e80009fa02
Timestamp: 1713286579 Timestamp [UCT]: 2024-04-16 16:56:19 Age [y:d:h:m:s]: 01:203:01:07:18
Block: 1001876 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 403779 RingCT/type: yes/0
Extra: 01cd5ce3c3798741e7d555fda968ef3a545d10b45949b31ede6eeea0e80009fa0202110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 16c645a9f2473198580c80a0aa3a1d5a51dda8ed257fb8a9ac3d764128d11851 0.600000000000 1462388 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": 1001886, "vin": [ { "gen": { "height": 1001876 } } ], "vout": [ { "amount": 600000000, "target": { "key": "16c645a9f2473198580c80a0aa3a1d5a51dda8ed257fb8a9ac3d764128d11851" } } ], "extra": [ 1, 205, 92, 227, 195, 121, 135, 65, 231, 213, 85, 253, 169, 104, 239, 58, 84, 93, 16, 180, 89, 73, 179, 30, 222, 110, 238, 160, 232, 0, 9, 250, 2, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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