Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6a6339d4be0ed7d89513bca2b28782ebe2f6573321a8939b8ccda028068a6f27

Tx prefix hash: ac413bed115e2729ade86734ebec76c12349d9c0b3bd5c94c82cf52f752df7a5
Tx public key: d434fed0826e7b8926e7cd87a78c3d3ef9ad334ea6dfc779e8a958160a15fca3
Timestamp: 1705306306 Timestamp [UCT]: 2024-01-15 08:11:46 Age [y:d:h:m:s]: 01:159:20:00:23
Block: 935717 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 375176 RingCT/type: yes/0
Extra: 01d434fed0826e7b8926e7cd87a78c3d3ef9ad334ea6dfc779e8a958160a15fca30211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d3c7fe99672603a21444d2547d9f941ea7b666186a6c1ec77e1c3a1139d06b82 0.600000000000 1393733 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": 935727, "vin": [ { "gen": { "height": 935717 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d3c7fe99672603a21444d2547d9f941ea7b666186a6c1ec77e1c3a1139d06b82" } } ], "extra": [ 1, 212, 52, 254, 208, 130, 110, 123, 137, 38, 231, 205, 135, 167, 140, 61, 62, 249, 173, 51, 78, 166, 223, 199, 121, 232, 169, 88, 22, 10, 21, 252, 163, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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