Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8fa9f0b8ed15b17bcba17b51bb4d25366ba8f2605730becc99ca9d63620e3744

Tx prefix hash: 8cc0cf56b11da948db8579bc1e64faf4e89e4ab6d0287fafb716f6ffc31a9906
Tx public key: fe82c1da8e976344792d3cb6d8909336c1e71b340c2066a7adc66b6ecbf7e6da
Timestamp: 1717616017 Timestamp [UCT]: 2024-06-05 19:33:37 Age [y:d:h:m:s]: 00:288:23:37:20
Block: 1037785 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206530 RingCT/type: yes/0
Extra: 01fe82c1da8e976344792d3cb6d8909336c1e71b340c2066a7adc66b6ecbf7e6da0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a391b43a025eef49b0f42afb921a2713d423c6117588ce7c59485ebea04578fe 0.600000000000 1506342 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": 1037795, "vin": [ { "gen": { "height": 1037785 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a391b43a025eef49b0f42afb921a2713d423c6117588ce7c59485ebea04578fe" } } ], "extra": [ 1, 254, 130, 193, 218, 142, 151, 99, 68, 121, 45, 60, 182, 216, 144, 147, 54, 193, 231, 27, 52, 12, 32, 102, 167, 173, 198, 107, 110, 203, 247, 230, 218, 2, 17, 0, 0, 0, 1, 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