Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3eeb87403ccc8d98f2ed6b536ec97cc8e1a51f017382ff9ed1f923127f8ed413

Tx prefix hash: 75340c6c4670221fefd52c0d683e67d45ca29172a0916b3f35efa7aa322922f0
Tx public key: d4fdcc27fc50b21b4cc8fb7cbc128a6e1dacb5dc793e3177d80444e5020dff74
Timestamp: 1672831617 Timestamp [UCT]: 2023-01-04 11:26:57 Age [y:d:h:m:s]: 02:093:06:21:45
Block: 667383 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 588319 RingCT/type: yes/0
Extra: 01d4fdcc27fc50b21b4cc8fb7cbc128a6e1dacb5dc793e3177d80444e5020dff7402110000000133af99f4000000000000000000

1 output(s) for total of 3.772967274000 dcy

stealth address amount amount idx
00: 08caa3fb9d76e1a394e0a6f1198a37077844a6e63e565763bc5e0be3b2c1b2b2 3.772967274000 1108552 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": 667393, "vin": [ { "gen": { "height": 667383 } } ], "vout": [ { "amount": 3772967274, "target": { "key": "08caa3fb9d76e1a394e0a6f1198a37077844a6e63e565763bc5e0be3b2c1b2b2" } } ], "extra": [ 1, 212, 253, 204, 39, 252, 80, 178, 27, 76, 200, 251, 124, 188, 18, 138, 110, 29, 172, 181, 220, 121, 62, 49, 119, 216, 4, 68, 229, 2, 13, 255, 116, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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