Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa48d39d097aa3697bc0411d9b15cb2c0619f55d5cf11820c53fb7df34520ad8

Tx prefix hash: 592cb3428d5d2b24a7ddab3ae3122265861c68a4e5a8db380b9855bad0b17ba1
Tx public key: 9e87b26705c98652cde0b440355028e86d243e8456aeb6100010647f12a62a20
Timestamp: 1726127720 Timestamp [UCT]: 2024-09-12 07:55:20 Age [y:d:h:m:s]: 00:101:10:14:40
Block: 1108353 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72567 RingCT/type: yes/0
Extra: 019e87b26705c98652cde0b440355028e86d243e8456aeb6100010647f12a62a2002110000001291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9fc7c10c4751814b8aa948679ae5c6fbde65eac767e4bf0d853f7ea41ef3fc6c 0.600000000000 1586220 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": 1108363, "vin": [ { "gen": { "height": 1108353 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9fc7c10c4751814b8aa948679ae5c6fbde65eac767e4bf0d853f7ea41ef3fc6c" } } ], "extra": [ 1, 158, 135, 178, 103, 5, 201, 134, 82, 205, 224, 180, 64, 53, 80, 40, 232, 109, 36, 62, 132, 86, 174, 182, 16, 0, 16, 100, 127, 18, 166, 42, 32, 2, 17, 0, 0, 0, 18, 145, 225, 60, 4, 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