Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c5d80654c5781893f6039a30b64074899c5d2bc945aa012d158e6f155568eb02

Tx prefix hash: 6882ee21f87b9442c564dc207c2c240f48cc407141d7966697c025dcabb1f2df
Tx public key: a9f7f9d5f95f49948fcbe65ef008a6fbf63a5d0af8662edef3f59ba49d6378f5
Timestamp: 1708708783 Timestamp [UCT]: 2024-02-23 17:19:43 Age [y:d:h:m:s]: 01:262:13:51:32
Block: 963944 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 446406 RingCT/type: yes/0
Extra: 01a9f7f9d5f95f49948fcbe65ef008a6fbf63a5d0af8662edef3f59ba49d6378f502110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c7ab7c9a6a3b71b751b883e0fc6900f3345316913320b47ddfe5410883d64664 0.600000000000 1423671 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": 963954, "vin": [ { "gen": { "height": 963944 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c7ab7c9a6a3b71b751b883e0fc6900f3345316913320b47ddfe5410883d64664" } } ], "extra": [ 1, 169, 247, 249, 213, 249, 95, 73, 148, 143, 203, 230, 94, 240, 8, 166, 251, 246, 58, 93, 10, 248, 102, 46, 222, 243, 245, 155, 164, 157, 99, 120, 245, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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