Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2a81079d8959783565be701039d99195f12b23d8c910f978b6c4811e032daa63

Tx prefix hash: 864db1629d6cb22d7f0917277c5fd9315e3a65b9da06ce55a382330dc8503985
Tx public key: 3dde739e2093cd348db6d9ac4a3a3928babe5d3e8ea0dcc9d0de268ef2d06ee3
Timestamp: 1705046306 Timestamp [UCT]: 2024-01-12 07:58:26 Age [y:d:h:m:s]: 01:124:09:02:31
Block: 933561 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 350026 RingCT/type: yes/0
Extra: 013dde739e2093cd348db6d9ac4a3a3928babe5d3e8ea0dcc9d0de268ef2d06ee302110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f6faffa4796a7267d3b6803e935d3096844e05e07887c03c96c009bf89f05c83 0.600000000000 1391525 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": 933571, "vin": [ { "gen": { "height": 933561 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f6faffa4796a7267d3b6803e935d3096844e05e07887c03c96c009bf89f05c83" } } ], "extra": [ 1, 61, 222, 115, 158, 32, 147, 205, 52, 141, 182, 217, 172, 74, 58, 57, 40, 186, 190, 93, 62, 142, 160, 220, 201, 208, 222, 38, 142, 242, 208, 110, 227, 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