Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 831068cabe0facfae868bb73cf306ace0fa2f9427a4d54c8cd5ed6101d2b4dbc

Tx prefix hash: d4435f1d7ff1e906e1df8737183a0d22795a981747f6c9e8fbe768428e6464ba
Tx public key: 6afd7c84e13df5a9627e910857eb11c1c4b619d168cd86d3e20140e49e9bc276
Timestamp: 1720508513 Timestamp [UCT]: 2024-07-09 07:01:53 Age [y:d:h:m:s]: 01:123:12:39:00
Block: 1061777 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 346806 RingCT/type: yes/0
Extra: 016afd7c84e13df5a9627e910857eb11c1c4b619d168cd86d3e20140e49e9bc27602110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 042ee6786b05111515f6d58eefbb766da9c528f9256ac015dcf71c308d55aca2 0.600000000000 1532272 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": 1061787, "vin": [ { "gen": { "height": 1061777 } } ], "vout": [ { "amount": 600000000, "target": { "key": "042ee6786b05111515f6d58eefbb766da9c528f9256ac015dcf71c308d55aca2" } } ], "extra": [ 1, 106, 253, 124, 132, 225, 61, 245, 169, 98, 126, 145, 8, 87, 235, 17, 193, 196, 182, 25, 209, 104, 205, 134, 211, 226, 1, 64, 228, 158, 155, 194, 118, 2, 17, 0, 0, 0, 4, 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