Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f3064c820954b576d951177900de24c0fe9398647a821c8b666a02a26dc8ae4c

Tx prefix hash: 79788756795a41fe13cb3dc49d6fe56711595e84b58f3be29b0a75d7566fd8f9
Tx public key: 14380f9fc0683c79bad8df4e4c262ec6effe50dbc39d51e291dc041f4a45b9ee
Timestamp: 1717426517 Timestamp [UCT]: 2024-06-03 14:55:17 Age [y:d:h:m:s]: 01:158:03:13:42
Block: 1036233 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 371588 RingCT/type: yes/0
Extra: 0114380f9fc0683c79bad8df4e4c262ec6effe50dbc39d51e291dc041f4a45b9ee02110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6328437fc691a57197277a38a56f34478391c864c481b0ae2a0f5d4f9520430e 0.600000000000 1504758 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": 1036243, "vin": [ { "gen": { "height": 1036233 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6328437fc691a57197277a38a56f34478391c864c481b0ae2a0f5d4f9520430e" } } ], "extra": [ 1, 20, 56, 15, 159, 192, 104, 60, 121, 186, 216, 223, 78, 76, 38, 46, 198, 239, 254, 80, 219, 195, 157, 81, 226, 145, 220, 4, 31, 74, 69, 185, 238, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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