Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 45055699b1eee171436d29c9873767c3fb228b2a6b9c86a8461c278107e641e1

Tx prefix hash: c378ad5b46387744d72aa3a867f99e8cd3f8ab05544c470b1327baeb8451951f
Tx public key: 3939d3e9d6d1e5085f4e6ad259d3fc7d046b2890b0e056c838559a9c8e0bc7d4
Timestamp: 1699585267 Timestamp [UCT]: 2023-11-10 03:01:07 Age [y:d:h:m:s]: 01:133:02:49:23
Block: 888311 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 356315 RingCT/type: yes/0
Extra: 013939d3e9d6d1e5085f4e6ad259d3fc7d046b2890b0e056c838559a9c8e0bc7d4021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.699289331000 dcy

stealth address amount amount idx
00: b6868e4a4d589703f9502729b5a77fa8fe5d3246143578b1b7643454164be06f 0.699289331000 1344250 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": 888321, "vin": [ { "gen": { "height": 888311 } } ], "vout": [ { "amount": 699289331, "target": { "key": "b6868e4a4d589703f9502729b5a77fa8fe5d3246143578b1b7643454164be06f" } } ], "extra": [ 1, 57, 57, 211, 233, 214, 209, 229, 8, 95, 78, 106, 210, 89, 211, 252, 125, 4, 107, 40, 144, 176, 224, 86, 200, 56, 85, 154, 156, 142, 11, 199, 212, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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