Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e23db75ea900e3e40e3998cfa4d64a4dd14ffe5931cce2bbdf7b0de2c4bc121f

Tx prefix hash: bb6c6227af68628b4c7209be1d001efc4ea64db30f63ea7f543502f491e4785c
Tx public key: df8000d47f80a3bb5b3c94211af1cc5e10d641fb2c510e013d9f59cd033a7e63
Timestamp: 1708859916 Timestamp [UCT]: 2024-02-25 11:18:36 Age [y:d:h:m:s]: 01:117:09:40:11
Block: 965204 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 344793 RingCT/type: yes/0
Extra: 01df8000d47f80a3bb5b3c94211af1cc5e10d641fb2c510e013d9f59cd033a7e630211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f4eeb3a8c285bd8e1bb6c500c288564915813d2b59c87aa1b70de4931400f4aa 0.600000000000 1424953 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": 965214, "vin": [ { "gen": { "height": 965204 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f4eeb3a8c285bd8e1bb6c500c288564915813d2b59c87aa1b70de4931400f4aa" } } ], "extra": [ 1, 223, 128, 0, 212, 127, 128, 163, 187, 91, 60, 148, 33, 26, 241, 204, 94, 16, 214, 65, 251, 44, 81, 14, 1, 61, 159, 89, 205, 3, 58, 126, 99, 2, 17, 0, 0, 0, 7, 122, 156, 244, 199, 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