← previous blocknext block →recent activity
Analyzing
Block #83,398,860
27 transactions · 18 stateful · 2026-06-24 14:03:38 UTC
Parallelism
81/100
Blocked
39%
Avg conflicts / tx
0.59
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,398,860 · 27 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w111w012w013w114w215w016w119w220w024w325w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x71632345…6ee9
0x34b655…2a6f
8 touches
6 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0x58397d66…a6bc
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x43e3decb…be40
0x34b655…2a6f
4 touches
1 conflict
0x4ca9afe5…748d
0x34b655…2a6f
4 touches
1 conflict
0x5f91ee13…5aef
0x34b655…2a6f
4 touches
1 conflict
0x7e6c970a…65af
0x34b655…2a6f
4 touches
1 conflict
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Perpl
6 conflicts on slot 0x7163234506…a86ee9
Audit this contract →
← previous block·next block →recent activity