Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b6f25d18a39031f8fa784dc95ee7bb943f63474b737fe83498e034f501476c3

Tx prefix hash: 8d9ea70509e8ad39a4fb7eac5b33fb6816325bb673100b73f2239710275890f6
Tx public key: 5f69cddf57bbc2c5faf49ffa649d51b00d258a0757e0c5ebd594b4bd3727b689
Timestamp: 1709021512 Timestamp [UCT]: 2024-02-27 08:11:52 Age [y:d:h:m:s]: 00:344:22:38:31
Block: 966548 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 246632 RingCT/type: yes/0
Extra: 015f69cddf57bbc2c5faf49ffa649d51b00d258a0757e0c5ebd594b4bd3727b6890211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f49d3a0f7227c8c115a7286f8adf48bd4166a1cd43b53577515f2a9b079acf06 0.600000000000 1426309 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": 966558, "vin": [ { "gen": { "height": 966548 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f49d3a0f7227c8c115a7286f8adf48bd4166a1cd43b53577515f2a9b079acf06" } } ], "extra": [ 1, 95, 105, 205, 223, 87, 187, 194, 197, 250, 244, 159, 250, 100, 157, 81, 176, 13, 37, 138, 7, 87, 224, 197, 235, 213, 148, 180, 189, 55, 39, 182, 137, 2, 17, 0, 0, 0, 2, 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