Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a197ab633971de334ed9da9bb54f71f6bfd78f388aff39faec03e8dbbbb4f49

Tx prefix hash: c3941610093993f4d19ab1d3602795992c93b5ffa8518f2b68a36b29523a78b1
Tx public key: 0745fa723b976e55d40b331ea839972c9e1266c5596cc3dc97581e3c3c29084b
Timestamp: 1710103843 Timestamp [UCT]: 2024-03-10 20:50:43 Age [y:d:h:m:s]: 01:038:13:22:26
Block: 975520 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288554 RingCT/type: yes/0
Extra: 010745fa723b976e55d40b331ea839972c9e1266c5596cc3dc97581e3c3c29084b0211000000070011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7c20ff30a497721cf229e1f02b5f1c87951e8f49afd5b9fe7f9f9c70fe4a8715 0.600000000000 1435493 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": 975530, "vin": [ { "gen": { "height": 975520 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7c20ff30a497721cf229e1f02b5f1c87951e8f49afd5b9fe7f9f9c70fe4a8715" } } ], "extra": [ 1, 7, 69, 250, 114, 59, 151, 110, 85, 212, 11, 51, 30, 168, 57, 151, 44, 158, 18, 102, 197, 89, 108, 195, 220, 151, 88, 30, 60, 60, 41, 8, 75, 2, 17, 0, 0, 0, 7, 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