← previous blocknext block →recent activity
Analyzing
Block #87,900,423
16 transactions · 13 stateful · 2026-07-15 10:49:56 UTC
Parallelism
81/100
Blocked
23%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,900,423 · 16 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
1w02w17w08w010w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe6fd79d8…6136
0x34b655…2a6f
6 touches
3 conflicts
0x7b6c252d…a696
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xd7ce55a7…0538
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x6cf1afa5…d70a
0x34b655…2a6f
4 touches
1 conflict
0x6cf1afa5…d70b
0x34b655…2a6f
4 touches
1 conflict
0x9ba6ae4a…90cb
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 0xe6fd79d82f…196136
Audit this contract →
← previous block·next block →recent activity