Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b2f35061b8ed0aeba52bcead246bbb419ababa855b4560c573284ada32a369a4

Tx prefix hash: fe3eb8c4b19c445b26272976f15ef1e6c9ba1281c328ad74a34e9491af0d0d73
Tx public key: 240d0a5897d3bdb191831ae711b9e24b42dd34a1d0217f3e5047a1cfc44dc444
Timestamp: 1581258024 Timestamp [UCT]: 2020-02-09 14:20:24 Age [y:d:h:m:s]: 04:323:00:44:29
Block: 61461 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1122908 RingCT/type: yes/0
Extra: 01240d0a5897d3bdb191831ae711b9e24b42dd34a1d0217f3e5047a1cfc44dc4440211000000084ac5aa02000000000000000000

1 output(s) for total of 384.027671230000 dcy

stealth address amount amount idx
00: 73de51fb498b798fbfedbf5bb812a372adb0e5810e94000fc1ef533670327322 384.027671230000 113270 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": 61471, "vin": [ { "gen": { "height": 61461 } } ], "vout": [ { "amount": 384027671230, "target": { "key": "73de51fb498b798fbfedbf5bb812a372adb0e5810e94000fc1ef533670327322" } } ], "extra": [ 1, 36, 13, 10, 88, 151, 211, 189, 177, 145, 131, 26, 231, 17, 185, 226, 75, 66, 221, 52, 161, 208, 33, 127, 62, 80, 71, 161, 207, 196, 77, 196, 68, 2, 17, 0, 0, 0, 8, 74, 197, 170, 2, 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