Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a641ad79bf7a895a6d5d6bcd8aa5148977d19a15fbea16678ae4b6227cfe0fc3

Tx prefix hash: 4cbdcaed63b00b77a9a71d160b951c04a2310bf32b3e8315f62bcc1c5a0df848
Tx public key: 5c5b5fd51616bda0b895aba10e27d98d603faf8211d6b44f44737bc7441a6625
Timestamp: 1727567053 Timestamp [UCT]: 2024-09-28 23:44:13 Age [y:d:h:m:s]: 00:103:15:56:04
Block: 1120292 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74111 RingCT/type: yes/0
Extra: 015c5b5fd51616bda0b895aba10e27d98d603faf8211d6b44f44737bc7441a6625021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2450c9e8c971847e520147d58882af3eb0680a81ede1bd3cac4f86bd3e4af484 0.600000000000 1602157 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": 1120302, "vin": [ { "gen": { "height": 1120292 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2450c9e8c971847e520147d58882af3eb0680a81ede1bd3cac4f86bd3e4af484" } } ], "extra": [ 1, 92, 91, 95, 213, 22, 22, 189, 160, 184, 149, 171, 161, 14, 39, 217, 141, 96, 63, 175, 130, 17, 214, 180, 79, 68, 115, 123, 199, 68, 26, 102, 37, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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