Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de32ab28ee5b002fd52ef3b98f2f56d0cc8e4c3ab85711d8b8cc49e2678c7f07

Tx prefix hash: e3639ce33e8c364fef1e5f023578c21d108cef77ec90b7aa3c99ac14ac9a7474
Tx public key: 8e107aca4eaeab47b9c279048446ff4be52ec20caea4e8b6a03d782405fe44c8
Timestamp: 1730730005 Timestamp [UCT]: 2024-11-04 14:20:05 Age [y:d:h:m:s]: 00:002:22:22:59
Block: 1146422 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 2108 RingCT/type: yes/0
Extra: 018e107aca4eaeab47b9c279048446ff4be52ec20caea4e8b6a03d782405fe44c80211000000081f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1bbb675b8d942779afcf9b168ae35ed99e6a93468421398b21d1428b83af650c 0.600000000000 1631065 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": 1146432, "vin": [ { "gen": { "height": 1146422 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1bbb675b8d942779afcf9b168ae35ed99e6a93468421398b21d1428b83af650c" } } ], "extra": [ 1, 142, 16, 122, 202, 78, 174, 171, 71, 185, 194, 121, 4, 132, 70, 255, 75, 229, 46, 194, 12, 174, 164, 232, 182, 160, 61, 120, 36, 5, 254, 68, 200, 2, 17, 0, 0, 0, 8, 31, 10, 83, 235, 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