Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 034c280e947306d30528f8164e61d68661cdfcd127cbc5733faa8fed1f532d7a

Tx prefix hash: 5400390d8d51981e0779337bf64fa0716648ba8be87c6aa6368c86f945a981f1
Tx public key: e1cbe19d6ffae7cbf1c0d2ea9b6f6ecb89ba39daa61194becab9f3a6811b5ba1
Timestamp: 1723125624 Timestamp [UCT]: 2024-08-08 14:00:24 Age [y:d:h:m:s]: 00:108:05:01:47
Block: 1083463 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 77414 RingCT/type: yes/0
Extra: 01e1cbe19d6ffae7cbf1c0d2ea9b6f6ecb89ba39daa61194becab9f3a6811b5ba1021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2476c03c249870e828dc54a1e78b712940bc9b8e6bce837618b199191f261eb0 0.600000000000 1557394 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": 1083473, "vin": [ { "gen": { "height": 1083463 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2476c03c249870e828dc54a1e78b712940bc9b8e6bce837618b199191f261eb0" } } ], "extra": [ 1, 225, 203, 225, 157, 111, 250, 231, 203, 241, 192, 210, 234, 155, 111, 110, 203, 137, 186, 57, 218, 166, 17, 148, 190, 202, 185, 243, 166, 129, 27, 91, 161, 2, 17, 0, 0, 0, 2, 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