← previous blocknext block →recent activity
Analyzing
Block #86,627,114
17 transactions · 12 stateful · 2026-07-09 12:54:48 UTC
Parallelism
71/100
Blocked
42%
Avg conflicts / tx
0.76
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,627,114 · 17 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
1w02w13w16w013w214w316w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1941b441…5889
0x34b655…2a6f
8 touches
6 conflicts
0xa29182a1…c12c
0x34b655…2a6f
6 touches
3 conflicts
0x80519201…5f47
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xe4ff807b…3da1
0x34b655…2a6f
6 touches
3 conflicts
0x9a36cb2e…0929
0x34b655…2a6f
6 touches
3 conflicts
0xaf98736d…8142
0x34b655…2a6f
4 touches
1 conflict
0xf8c2f856…9b1b
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 0x1941b4413e…0c5889
Audit this contract →
← previous block·next block →recent activity