Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 718c7f4f99a343c79f41b57c438ab4e1366a6e3b01f116be3c03d0dae42ab198

Tx prefix hash: a0c479d14ded9566f8c34325f0a0d80520bb5bff70b57d1385289fb6feb3ffe3
Tx public key: 65c09cf34dd3841e60ad372425099d86fdf3962ed0d7774ee517e9ef66b621a4
Timestamp: 1728947184 Timestamp [UCT]: 2024-10-14 23:06:24 Age [y:d:h:m:s]: 00:087:06:06:17
Block: 1131734 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 62361 RingCT/type: yes/0
Extra: 0165c09cf34dd3841e60ad372425099d86fdf3962ed0d7774ee517e9ef66b621a4021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ee73f932e636edc6e0c1cc520e05ecbe0a0d9a8ad16df730304d7ace0f7facbd 0.600000000000 1614639 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": 1131744, "vin": [ { "gen": { "height": 1131734 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ee73f932e636edc6e0c1cc520e05ecbe0a0d9a8ad16df730304d7ace0f7facbd" } } ], "extra": [ 1, 101, 192, 156, 243, 77, 211, 132, 30, 96, 173, 55, 36, 37, 9, 157, 134, 253, 243, 150, 46, 208, 215, 119, 78, 229, 23, 233, 239, 102, 182, 33, 164, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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