← previous blocknext block →recent activity
Analyzing
Block #86,624,185
23 transactions · 18 stateful · 2026-07-09 12:35:15 UTC
Parallelism
74/100
Blocked
44%
Avg conflicts / tx
0.78
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,624,185 · 23 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w17w09w110w113w015w216w320w121w422w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x1941b441…5889
0x34b655…2a6f
8 touches
6 conflicts
0x2b95e778…d7d0
0x34b655…2a6f
6 touches
3 conflicts
0x24de48ed…b934
0x34b655…2a6f
4 touches
1 conflict
0x272e5bd6…252d
0x34b655…2a6f
4 touches
1 conflict
0x8c42f949…c9d4
0x851145…3f07
4 touches
1 conflict
0x08102aaf…36b2
0x34b655…2a6f
4 touches
1 conflict
0x17c3727d…cb0e
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity