Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 666f5a269224262fccdd7e3befc382be77eb70cdbe9f975440b066f165171ab5

Tx prefix hash: bdc5fda40eff4829812a5fb7dbb776e1e9ff972cdc897d3d2e87822b1c19abb4
Tx public key: 969247a3379f3516ed9d9e87cae5f6e35682ca67f8ad8dd956d3609a741b37e6
Timestamp: 1710453686 Timestamp [UCT]: 2024-03-14 22:01:26 Age [y:d:h:m:s]: 01:026:00:28:41
Block: 978427 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 279568 RingCT/type: yes/0
Extra: 01969247a3379f3516ed9d9e87cae5f6e35682ca67f8ad8dd956d3609a741b37e60211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9ad05ef3c07bae827b6807c11f43262af4130c3b2602ebf2b1ee41f076b39090 0.600000000000 1438454 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": 978437, "vin": [ { "gen": { "height": 978427 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9ad05ef3c07bae827b6807c11f43262af4130c3b2602ebf2b1ee41f076b39090" } } ], "extra": [ 1, 150, 146, 71, 163, 55, 159, 53, 22, 237, 157, 158, 135, 202, 229, 246, 227, 86, 130, 202, 103, 248, 173, 141, 217, 86, 211, 96, 154, 116, 27, 55, 230, 2, 17, 0, 0, 0, 5, 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