← previous blocknext block →recent activity
Analyzing
Block #87,496,532
23 transactions · 18 stateful · 2026-07-13 13:47:40 UTC
Parallelism
78/100
Blocked
56%
Avg conflicts / tx
0.83
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,496,532 · 23 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
1w02w14w15w06w111w212w314w015w116w017w118w220w321w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb670a63e…ead8
0x34b655…2a6f
8 touches
6 conflicts
0x24f6d4ca…c33b
0x34b655…2a6f
6 touches
3 conflicts
0x03fb27fd…0c06
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x2a49f3bf…713b
0x34b655…2a6f
6 touches
3 conflicts
0x366c7d57…0ed1
0x34b655…2a6f
6 touches
3 conflicts
0x49f4036c…3e68
0x34b655…2a6f
6 touches
3 conflicts
0x4c188934…158e
0x34b655…2a6f
6 touches
3 conflicts
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
6 conflicts on slot 0xb670a63ebd…04ead8
Audit this contract →
← previous block·next block →recent activity