Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e7cf2c9212a89c7088cad5f1b15f50b94a01db395207bea9243103cc0f474bdf

Tx prefix hash: 77afa32bd263240b4d5020caeac5309745824c34b04cd0d93227a19147d9ae52
Tx public key: c24c7fad7b60bb56b20b74dd6c35b5e5cf9988faadf700d375426e2f0d8d5b08
Timestamp: 1674998363 Timestamp [UCT]: 2023-01-29 13:19:23 Age [y:d:h:m:s]: 01:290:15:26:41
Block: 685358 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 468652 RingCT/type: yes/0
Extra: 01c24c7fad7b60bb56b20b74dd6c35b5e5cf9988faadf700d375426e2f0d8d5b0802110000000f835e4d22000000000000000000

1 output(s) for total of 3.289458223000 dcy

stealth address amount amount idx
00: 35d94d889bbf8a4e60bbff373bee4efe007ad06b4371eb681956507540820b77 3.289458223000 1127665 of 0

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": 685368, "vin": [ { "gen": { "height": 685358 } } ], "vout": [ { "amount": 3289458223, "target": { "key": "35d94d889bbf8a4e60bbff373bee4efe007ad06b4371eb681956507540820b77" } } ], "extra": [ 1, 194, 76, 127, 173, 123, 96, 187, 86, 178, 11, 116, 221, 108, 53, 181, 229, 207, 153, 136, 250, 173, 247, 0, 211, 117, 66, 110, 47, 13, 141, 91, 8, 2, 17, 0, 0, 0, 15, 131, 94, 77, 34, 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