Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc50d02662b8364126503d5ced6e00120b9084e222bc58eef5efef2bb412a27c

Tx prefix hash: e4b60c11db8006208719ac8dd27d8d3f58247d189553e97fe43e1fa8be7b32c1
Tx public key: f96a286771f34059a311353a139ec0c35a04ae26e833f3b2be971c7ceaf4d8ac
Timestamp: 1706549357 Timestamp [UCT]: 2024-01-29 17:29:17 Age [y:d:h:m:s]: 01:139:17:40:44
Block: 946024 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 360892 RingCT/type: yes/0
Extra: 01f96a286771f34059a311353a139ec0c35a04ae26e833f3b2be971c7ceaf4d8ac0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8a1e96a8a2808e5236a20297dc911161e1bee2a7ef176a2207bffd4564fe7441 0.600000000000 1404354 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": 946034, "vin": [ { "gen": { "height": 946024 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8a1e96a8a2808e5236a20297dc911161e1bee2a7ef176a2207bffd4564fe7441" } } ], "extra": [ 1, 249, 106, 40, 103, 113, 243, 64, 89, 163, 17, 53, 58, 19, 158, 192, 195, 90, 4, 174, 38, 232, 51, 243, 178, 190, 151, 28, 124, 234, 244, 216, 172, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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