Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a27a6eae3c833061d82e0750d7ce3d203be6c05a12658ba9bc525ebe21f98d3d

Tx prefix hash: 579f815bdc3e045f1f67e18be44705f1c0f5f0b1e30ef617ab6494f1904e5ff4
Tx public key: e61493a5ba609b69bac5e3180784d11467726a0c3f1b258657d32c8d6512d96a
Timestamp: 1704668239 Timestamp [UCT]: 2024-01-07 22:57:19 Age [y:d:h:m:s]: 01:049:13:14:52
Block: 930428 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 296494 RingCT/type: yes/0
Extra: 01e61493a5ba609b69bac5e3180784d11467726a0c3f1b258657d32c8d6512d96a0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f0665a36fe95e68f37383291e185da0282d42e18505654fdf8a3516a5378cba8 0.600000000000 1388310 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": 930438, "vin": [ { "gen": { "height": 930428 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f0665a36fe95e68f37383291e185da0282d42e18505654fdf8a3516a5378cba8" } } ], "extra": [ 1, 230, 20, 147, 165, 186, 96, 155, 105, 186, 197, 227, 24, 7, 132, 209, 20, 103, 114, 106, 12, 63, 27, 37, 134, 87, 211, 44, 141, 101, 18, 217, 106, 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