Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a8fa9795837b5a2601e03b8fa225904b507c80c05008b5e2ba0470b075cb57fc

Tx prefix hash: 3999bb51d69980e32a852be6bd400a5ebcb7d08f974b6302d0b433a64f835917
Tx public key: 8bee42115717d6ba1208a79d18ca9c9797d9337a477ec50a089a299e03b8e151
Timestamp: 1720094043 Timestamp [UCT]: 2024-07-04 11:54:03 Age [y:d:h:m:s]: 00:278:06:39:38
Block: 1058332 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198826 RingCT/type: yes/0
Extra: 018bee42115717d6ba1208a79d18ca9c9797d9337a477ec50a089a299e03b8e1510211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ffaa5bfa991056e6bca90528c881ec6e1225780d715c5508c1a69b5799cb94f1 0.600000000000 1528785 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": 1058342, "vin": [ { "gen": { "height": 1058332 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ffaa5bfa991056e6bca90528c881ec6e1225780d715c5508c1a69b5799cb94f1" } } ], "extra": [ 1, 139, 238, 66, 17, 87, 23, 214, 186, 18, 8, 167, 157, 24, 202, 156, 151, 151, 217, 51, 122, 71, 126, 197, 10, 8, 154, 41, 158, 3, 184, 225, 81, 2, 17, 0, 0, 0, 5, 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