Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eeb9b391e8b38ba65c07e0f838081f04ae210718f2495d0f48ca4c829f131422

Tx prefix hash: dc41d0f4d7c0030d8bef13f65ef40febd423d4347f4dfca15ec4196362f290cd
Tx public key: 41da4dce702c583960cefec564fe3b9db28e526d375902172411cadf61e41e79
Timestamp: 1632157086 Timestamp [UCT]: 2021-09-20 16:58:06 Age [y:d:h:m:s]: 03:236:01:09:08
Block: 337659 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 944536 RingCT/type: yes/0
Extra: 0141da4dce702c583960cefec564fe3b9db28e526d375902172411cadf61e41e7902110000002e5d7cc334000000000000000000

1 output(s) for total of 46.687003397000 dcy

stealth address amount amount idx
00: 40bbf1d79f8efd08934f5b34fbb52283da2dbe608aa5af4fefa6c414ba3f67e1 46.687003397000 695200 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": 337669, "vin": [ { "gen": { "height": 337659 } } ], "vout": [ { "amount": 46687003397, "target": { "key": "40bbf1d79f8efd08934f5b34fbb52283da2dbe608aa5af4fefa6c414ba3f67e1" } } ], "extra": [ 1, 65, 218, 77, 206, 112, 44, 88, 57, 96, 206, 254, 197, 100, 254, 59, 157, 178, 142, 82, 109, 55, 89, 2, 23, 36, 17, 202, 223, 97, 228, 30, 121, 2, 17, 0, 0, 0, 46, 93, 124, 195, 52, 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