Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 693ac7ff83b499dc207e293317673e1f9497a6b64619217e879c719efe86b5b1

Tx prefix hash: 789a754341e893e35822407d4fe2050d83f62d25b557cf35fefe484af42d02b2
Tx public key: eb532e548d6fee05aeff896f00c3d9bf7a6e4cf70c8559891248fd5ad5fdbca8
Timestamp: 1710890495 Timestamp [UCT]: 2024-03-19 23:21:35 Age [y:d:h:m:s]: 00:225:07:49:55
Block: 982051 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161307 RingCT/type: yes/0
Extra: 01eb532e548d6fee05aeff896f00c3d9bf7a6e4cf70c8559891248fd5ad5fdbca802110000000752d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 91ffb98aed88604b7fce8108ec15bc853c289ef0e8b9d212412f25f060005ffb 0.600000000000 1442154 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": 982061, "vin": [ { "gen": { "height": 982051 } } ], "vout": [ { "amount": 600000000, "target": { "key": "91ffb98aed88604b7fce8108ec15bc853c289ef0e8b9d212412f25f060005ffb" } } ], "extra": [ 1, 235, 83, 46, 84, 141, 111, 238, 5, 174, 255, 137, 111, 0, 195, 217, 191, 122, 110, 76, 247, 12, 133, 89, 137, 18, 72, 253, 90, 213, 253, 188, 168, 2, 17, 0, 0, 0, 7, 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