Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f2a115390a946433ce7ec713c6b1544c07d5bbc31f729989d971c8bc6ffd91b

Tx prefix hash: f40ddda212d6f90f79febbf51b364b8715840e5e29baf034b16ed07ec5c6b8fa
Tx public key: 5565f26eadac0cf1e3dac62ccda30ff7a0c2f31e56b6f65853723375d565cc64
Timestamp: 1579273005 Timestamp [UCT]: 2020-01-17 14:56:45 Age [y:d:h:m:s]: 04:294:08:14:54
Block: 47705 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1099687 RingCT/type: yes/0
Extra: 015565f26eadac0cf1e3dac62ccda30ff7a0c2f31e56b6f65853723375d565cc6402110000000a49b77a3d000000000000000000

1 output(s) for total of 426.543137639000 dcy

stealth address amount amount idx
00: 6aa18533b28955232cc4fc1ef1472b515a04dadfc86b1cf3982bba87abaea8b2 426.543137639000 88116 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": 47715, "vin": [ { "gen": { "height": 47705 } } ], "vout": [ { "amount": 426543137639, "target": { "key": "6aa18533b28955232cc4fc1ef1472b515a04dadfc86b1cf3982bba87abaea8b2" } } ], "extra": [ 1, 85, 101, 242, 110, 173, 172, 12, 241, 227, 218, 198, 44, 205, 163, 15, 247, 160, 194, 243, 30, 86, 182, 246, 88, 83, 114, 51, 117, 213, 101, 204, 100, 2, 17, 0, 0, 0, 10, 73, 183, 122, 61, 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