Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c25079830e4bc6319b79b3579ea081cb67287ff7c6c13d356031e23df48016b5

Tx prefix hash: 31ab14a245b4eec544ae6ef9edc3a96c0110c6c7796101495f1ca4df0c75a22c
Tx public key: 737983b95f625ee8f1e49f49c86fae5506242bb23238cd95cc823f353b37f1c8
Timestamp: 1735021916 Timestamp [UCT]: 2024-12-24 06:31:56 Age [y:d:h:m:s]: 00:100:23:48:38
Block: 1181980 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 71961 RingCT/type: yes/0
Extra: 01737983b95f625ee8f1e49f49c86fae5506242bb23238cd95cc823f353b37f1c80211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6c62bf6175fa39fe8afe0da0236b484fd58b4a8ecca716f9d5c21b13e83f00a7 0.600000000000 1668409 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": 1181990, "vin": [ { "gen": { "height": 1181980 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6c62bf6175fa39fe8afe0da0236b484fd58b4a8ecca716f9d5c21b13e83f00a7" } } ], "extra": [ 1, 115, 121, 131, 185, 95, 98, 94, 232, 241, 228, 159, 73, 200, 111, 174, 85, 6, 36, 43, 178, 50, 56, 205, 149, 204, 130, 63, 53, 59, 55, 241, 200, 2, 17, 0, 0, 0, 3, 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