Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f484fcd4e796fe153131b68a315533b69f12e28a4e441eff156d4fc6c58d5f15

Tx prefix hash: a53b455c543af53236fd8e2c3391e5990b53b090745b9bae9aa0367f50d0a6c6
Tx public key: f84f1c0852e72a3ac2b11843a50bb0b732b6d3bd2ae4d9c8c74475ca864f12be
Timestamp: 1719739816 Timestamp [UCT]: 2024-06-30 09:30:16 Age [y:d:h:m:s]: 00:268:10:18:40
Block: 1055395 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 191786 RingCT/type: yes/0
Extra: 01f84f1c0852e72a3ac2b11843a50bb0b732b6d3bd2ae4d9c8c74475ca864f12be0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 70e51faec34ae0f62309e44b8abbe7caffaf17500340e0571ebe7bcf4dd23054 0.600000000000 1525794 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": 1055405, "vin": [ { "gen": { "height": 1055395 } } ], "vout": [ { "amount": 600000000, "target": { "key": "70e51faec34ae0f62309e44b8abbe7caffaf17500340e0571ebe7bcf4dd23054" } } ], "extra": [ 1, 248, 79, 28, 8, 82, 231, 42, 58, 194, 177, 24, 67, 165, 11, 176, 183, 50, 182, 211, 189, 42, 228, 217, 200, 199, 68, 117, 202, 134, 79, 18, 190, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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