Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f61c8941eef1b4c12089841b5611a6a803ef5d7305e11bab814f43331c1d4599

Tx prefix hash: e0f2ebaea43f45c758fb0e15bf97d2e311b8037063f13dfa8a171f064a150dee
Tx public key: c7b925afdd9d45c00aec498db98e863ee80886045b51630b890ee8a2df8706cd
Timestamp: 1677162835 Timestamp [UCT]: 2023-02-23 14:33:55 Age [y:d:h:m:s]: 02:037:07:22:26
Block: 703297 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 548252 RingCT/type: yes/0
Extra: 01c7b925afdd9d45c00aec498db98e863ee80886045b51630b890ee8a2df8706cd021100000001faf35c9c000000000000000000

1 output(s) for total of 2.868699086000 dcy

stealth address amount amount idx
00: 0fa1ad4ca1a5d960cce935667be580ef69059d2125fd677f01bab40d8507e46c 2.868699086000 1146870 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": 703307, "vin": [ { "gen": { "height": 703297 } } ], "vout": [ { "amount": 2868699086, "target": { "key": "0fa1ad4ca1a5d960cce935667be580ef69059d2125fd677f01bab40d8507e46c" } } ], "extra": [ 1, 199, 185, 37, 175, 221, 157, 69, 192, 10, 236, 73, 141, 185, 142, 134, 62, 232, 8, 134, 4, 91, 81, 99, 11, 137, 14, 232, 162, 223, 135, 6, 205, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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