Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 63c416d7b4bb16bec246a2e0757272d92101ec790f716bc8cc301a2bad6d34d0

Tx prefix hash: a0e6b711d97272d50e3068afeb386835d423303052b3a0025a9fba7223a56388
Tx public key: fd7fc250fcf0e1c3393de9a5ee661ac4425a28bbb4574cc5053e096d252fd35f
Timestamp: 1729773587 Timestamp [UCT]: 2024-10-24 12:39:47 Age [y:d:h:m:s]: 01:015:12:50:20
Block: 1138540 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 269489 RingCT/type: yes/0
Extra: 01fd7fc250fcf0e1c3393de9a5ee661ac4425a28bbb4574cc5053e096d252fd35f0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 72214a7c4f570763d5b83d6521fce3eb2f764ea7f1a45018579a65b89f2ad7cb 0.600000000000 1622225 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": 1138550, "vin": [ { "gen": { "height": 1138540 } } ], "vout": [ { "amount": 600000000, "target": { "key": "72214a7c4f570763d5b83d6521fce3eb2f764ea7f1a45018579a65b89f2ad7cb" } } ], "extra": [ 1, 253, 127, 194, 80, 252, 240, 225, 195, 57, 61, 233, 165, 238, 102, 26, 196, 66, 90, 40, 187, 180, 87, 76, 197, 5, 62, 9, 109, 37, 47, 211, 95, 2, 17, 0, 0, 0, 1, 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