← previous blocknext block →recent activity
Analyzing
Block #87,913,599
10 transactions · 7 stateful · 2026-07-15 12:18:04 UTC
Parallelism
80/100
Blocked
29%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,913,599 · 10 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
1w04w06w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa3b15389…624e
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x2000b734…5e5a
0x34b655…2a6f
4 touches
1 conflict
0x93b4422b…b4f4
0x34b655…2a6f
4 touches
1 conflict
0x13510de3…1c68
0x34b655…2a6f
2 touches
0 conflicts
0x2ccd8c61…48f2
0x34b655…2a6f
2 touches
0 conflicts
0x36dc74c7…182a
0x34b655…2a6f
2 touches
0 conflicts
0x3726966a…669d
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 0xa3b15389a2…67624e
Audit this contract →
← previous block·next block →recent activity