← previous blocknext block →recent activity
Analyzing
Block #87,341,898
13 transactions · 11 stateful · 2026-07-12 20:33:35 UTC
Parallelism
85/100
Blocked
18%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,341,898 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w08w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdfd64ea5…015c
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x410b84ab…1dbc
0x34b655…2a6f
4 touches
1 conflict
0xd4726587…6289
0x34b655…2a6f
4 touches
1 conflict
0x347327ff…3863
0x34b655…2a6f
2 touches
0 conflicts
0x3ce98929…9a9b
0x34b655…2a6f
2 touches
0 conflicts
0x408e66bb…3d6b
0x34b655…2a6f
2 touches
0 conflicts
0x4caf91f9…8ab5
0x34b655…2a6f
2 touches
0 conflicts
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
1 conflict on slot 0xdfd64ea578…1e015c
Audit this contract →
← previous block·next block →recent activity