Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e89f25bf1eff39a04221cda18935c7d5e841b597830330abed2d3e00cb1f0e2

Tx prefix hash: 8a42a208eab49563229a2534156e8274ed0fb5659547368b2c21ed54ce8a7065
Tx public key: 872e0f5da13b2f9927fa1049f404f8d593bc253e40b49169953297a17fd910f9
Timestamp: 1724921784 Timestamp [UCT]: 2024-08-29 08:56:24 Age [y:d:h:m:s]: 00:132:23:45:00
Block: 1098354 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 95125 RingCT/type: yes/0
Extra: 01872e0f5da13b2f9927fa1049f404f8d593bc253e40b49169953297a17fd910f902110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 62afe434875711178bac8d3af62ce05d8550842b086d25cc4b1eebdcb2b4c5d1 0.600000000000 1574043 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": 1098364, "vin": [ { "gen": { "height": 1098354 } } ], "vout": [ { "amount": 600000000, "target": { "key": "62afe434875711178bac8d3af62ce05d8550842b086d25cc4b1eebdcb2b4c5d1" } } ], "extra": [ 1, 135, 46, 15, 93, 161, 59, 47, 153, 39, 250, 16, 73, 244, 4, 248, 213, 147, 188, 37, 62, 64, 180, 145, 105, 149, 50, 151, 161, 127, 217, 16, 249, 2, 17, 0, 0, 0, 8, 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