Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2fc07cf25a0daa862253bb381904ecaf978c24b5d09082394a3fc9a39683f82a

Tx prefix hash: bd6c80f8b31d196ac8b1dc6d5a6789bd28ac51dd1a8dd96c36cdf2de813aa2f5
Tx public key: 5ec9b88a1c4a1b9522c3f1abc0d57c6945e9144c9e45ed6ca11f5a67bc4639d3
Timestamp: 1721069008 Timestamp [UCT]: 2024-07-15 18:43:28 Age [y:d:h:m:s]: 00:333:15:32:41
Block: 1066436 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0811 kB
Tx version: 2 No of confirmations: 238344 RingCT/type: yes/0
Extra: 015ec9b88a1c4a1b9522c3f1abc0d57c6945e9144c9e45ed6ca11f5a67bc4639d3

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fe6236b6f61005534f6c437bb5ffa982412b915c97bcfc4d8f458369839e5534 0.600000000000 1537031 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": 1066446, "vin": [ { "gen": { "height": 1066436 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fe6236b6f61005534f6c437bb5ffa982412b915c97bcfc4d8f458369839e5534" } } ], "extra": [ 1, 94, 201, 184, 138, 28, 74, 27, 149, 34, 195, 241, 171, 192, 213, 124, 105, 69, 233, 20, 76, 158, 69, 237, 108, 161, 31, 90, 103, 188, 70, 57, 211 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8