← previous blocknext block →recent activity
Analyzing
Block #87,715,888
21 transactions · 20 stateful · 2026-07-14 14:15:30 UTC
Parallelism
81/100
Blocked
35%
Avg conflicts / tx
0.57
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,715,888 · 21 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
2w05w06w17w29w110w211w312w219w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc0fb0790…a482
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x1321736a…43e3
0x34b655…2a6f
4 touches
1 conflict
0x3590cc5e…a59b
0x34b655…2a6f
4 touches
1 conflict
0x4a1e17cf…f6e3
0x34b655…2a6f
4 touches
1 conflict
0x4fc141d9…bb36
0x34b655…2a6f
4 touches
1 conflict
0x4fc141d9…bb37
0x34b655…2a6f
4 touches
1 conflict
0x74fd0a9b…3aaa
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 0xc0fb0790fb…63a482
Audit this contract →
← previous block·next block →recent activity