Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5424a05d58cb6b377f5e3c753a8b01dca056436e2222fae2574e71d828c4a583

Tx prefix hash: bddd3fe2a4629b8ddab0d0b5f52d578fee505a63cf5143739c6d19b258d3fba1
Tx public key: 96a0c375797ce895dc1fc7b8193ac056f9ee7f791aebbb9da8bbc0125dcb08f1
Timestamp: 1696070723 Timestamp [UCT]: 2023-09-30 10:45:23 Age [y:d:h:m:s]: 01:238:04:13:15
Block: 859378 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 431318 RingCT/type: yes/0
Extra: 0196a0c375797ce895dc1fc7b8193ac056f9ee7f791aebbb9da8bbc0125dcb08f10211000000054b8f5122000000000000000000

1 output(s) for total of 0.872015057000 dcy

stealth address amount amount idx
00: e4d755b68fbc8f217547fdd08cf0ca0b2ef9af6837f706f15bf4ed8938e1d0eb 0.872015057000 1313602 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": 859388, "vin": [ { "gen": { "height": 859378 } } ], "vout": [ { "amount": 872015057, "target": { "key": "e4d755b68fbc8f217547fdd08cf0ca0b2ef9af6837f706f15bf4ed8938e1d0eb" } } ], "extra": [ 1, 150, 160, 195, 117, 121, 124, 232, 149, 220, 31, 199, 184, 25, 58, 192, 86, 249, 238, 127, 121, 26, 235, 187, 157, 168, 187, 192, 18, 93, 203, 8, 241, 2, 17, 0, 0, 0, 5, 75, 143, 81, 34, 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