← previous blocknext block →recent activity
Analyzing
Block #86,257,842
19 transactions · 19 stateful · 2026-07-07 19:46:04 UTC
Parallelism
79/100
Blocked
53%
Avg conflicts / tx
0.74
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,257,842 · 19 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w27w38w19w211w012w013w314w117w118w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x07bb3f5a…617e
0x34b655…2a6f
8 touches
6 conflicts
0xb503dcab…7c61
0x34b655…2a6f
6 touches
3 conflicts
0xec0e0220…cb90
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xd800e635…b1d7
0x34b655…2a6f
6 touches
3 conflicts
0x42bb0ac5…6b33
0x34b655…2a6f
4 touches
1 conflict
0x521e7b60…777f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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 0x07bb3f5a12…2d617e
Audit this contract →
← previous block·next block →recent activity