Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 34a6ea1efbd6e81d90e84379e26e86155eba14e3888c9a053a372cbc0f447524

Tx prefix hash: f61f1ee6df2e90a8ef9c33059240befab5d578c4470ea3da40142579ac7a782f
Tx public key: e080e4fcd6f711cf24837e832025c9b63c2f89b4c2c31068fd8208170142746c
Timestamp: 1729160012 Timestamp [UCT]: 2024-10-17 10:13:32 Age [y:d:h:m:s]: 00:196:22:47:09
Block: 1133498 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 140556 RingCT/type: yes/0
Extra: 01e080e4fcd6f711cf24837e832025c9b63c2f89b4c2c31068fd8208170142746c02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4c38c64865c8e09d3ddf7acba5d108c4d39e94a9f6c6d76ca86200bffa517582 0.600000000000 1616621 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": 1133508, "vin": [ { "gen": { "height": 1133498 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4c38c64865c8e09d3ddf7acba5d108c4d39e94a9f6c6d76ca86200bffa517582" } } ], "extra": [ 1, 224, 128, 228, 252, 214, 247, 17, 207, 36, 131, 126, 131, 32, 37, 201, 182, 60, 47, 137, 180, 194, 195, 16, 104, 253, 130, 8, 23, 1, 66, 116, 108, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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