← previous blocknext block →recent activity
Analyzing
Block #87,718,241
16 transactions · 15 stateful · 2026-07-14 14:31:20 UTC
Parallelism
69/100
Blocked
40%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,718,241 · 16 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
1w02w05w06w17w28w310w412w115w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5f234b05…db39
0x34b655…2a6f
6 touches
3 conflicts
0x5e0b8bbe…377b
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x5f147a94…c7fb
0x34b655…2a6f
6 touches
3 conflicts
0xc2099fec…321d
0x34b655…2a6f
6 touches
3 conflicts
0x67905f6e…02a1
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x8b818135…eff8
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
3 conflicts on slot 0x5f234b05a2…82db39
Audit this contract →
← previous block·next block →recent activity