← previous blocknext block →recent activity
Analyzing
Block #87,518,577
19 transactions · 14 stateful · 2026-07-13 16:15:20 UTC
Parallelism
79/100
Blocked
29%
Avg conflicts / tx
0.47
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,518,577 · 19 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
5w06w17w211w314w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc36fa358…24cb
0x34b655…2a6f
8 touches
6 conflicts
0x3646c884…13db
0x34b655…2a6f
6 touches
3 conflicts
0x69028386…61a4
0x34b655…2a6f
6 touches
3 conflicts
0x3cb4b659…f735
0x34b655…2a6f
4 touches
1 conflict
0x4b24290b…acb4
0x34b655…2a6f
4 touches
1 conflict
0x4b43f348…e4a6
0x34b655…2a6f
4 touches
1 conflict
0x76ebf9c2…e0ef
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4a2
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
6 conflicts on slot 0xc36fa35805…6f24cb
Audit this contract →
← previous block·next block →recent activity