← previous blocknext block →recent activity
Analyzing
Block #87,904,763
10 transactions · 8 stateful · 2026-07-15 11:18:57 UTC
Parallelism
70/100
Blocked
38%
Avg conflicts / tx
0.6
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,904,763 · 10 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
2w03w15w06w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa013ecc1…7c8f
0x34b655…2a6f
6 touches
3 conflicts
0x822bd4f1…6b3a
0x34b655…2a6f
6 touches
3 conflicts
0x28d4261c…56c7
0x34b655…2a6f
4 touches
1 conflict
0x28d4261c…56c8
0x34b655…2a6f
4 touches
1 conflict
0x35cfae1b…c1f8
0x34b655…2a6f
4 touches
1 conflict
0x44d24653…fa2f
0x34b655…2a6f
4 touches
1 conflict
0x4e782273…1690
0x34b655…2a6f
4 touches
1 conflict
0x6c70c92a…5f97
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 0xa013ecc17b…017c8f
Audit this contract →
← previous block·next block →recent activity