Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6736aa3b9084ddca24c5e90e0bf8a66eea7e26e5f960517dd654bacdf3cbff7b

Tx prefix hash: 27a812e3b4a75c36225ba63375c2cbd6397ba17ccb3682f71f8a95247174d91f
Tx public key: bafc591d09526d260c18fe4443dc8b55e8e14189d10e45b039c8571377e69732
Timestamp: 1675209950 Timestamp [UCT]: 2023-02-01 00:05:50 Age [y:d:h:m:s]: 02:065:23:22:35
Block: 687100 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 568766 RingCT/type: yes/0
Extra: 01bafc591d09526d260c18fe4443dc8b55e8e14189d10e45b039c8571377e697320211000000035029cbac000000000000000000

1 output(s) for total of 3.246069059000 dcy

stealth address amount amount idx
00: 2c59c4c0c8dc52e94d2099382e0cb70208b36aa57f9ea3798be751fd398ffa57 3.246069059000 1129654 of 0

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": 687110, "vin": [ { "gen": { "height": 687100 } } ], "vout": [ { "amount": 3246069059, "target": { "key": "2c59c4c0c8dc52e94d2099382e0cb70208b36aa57f9ea3798be751fd398ffa57" } } ], "extra": [ 1, 186, 252, 89, 29, 9, 82, 109, 38, 12, 24, 254, 68, 67, 220, 139, 85, 232, 225, 65, 137, 209, 14, 69, 176, 57, 200, 87, 19, 119, 230, 151, 50, 2, 17, 0, 0, 0, 3, 80, 41, 203, 172, 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