← previous blocknext block →recent activity
Analyzing
Block #87,879,914
24 transactions · 12 stateful · 2026-07-15 08:32:44 UTC
Parallelism
88/100
Blocked
17%
Avg conflicts / tx
0.13
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,879,914 · 24 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w08w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x367b69ad…33d8
0x34b655…2a6f
4 touches
1 conflict
0x367b69ad…33d9
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4ab
0x34b655…2a6f
4 touches
1 conflict
0x4acbdbcf…a8c6
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
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
1 conflict on slot 0x367b69ad60…4333d8
Audit this contract →
← previous block·next block →recent activity