← previous blocknext block →recent activity
Analyzing
Block #87,524,877
17 transactions · 15 stateful · 2026-07-13 16:57:55 UTC
Parallelism
65/100
Blocked
47%
Avg conflicts / tx
0.65
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,524,877 · 17 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w07w110w211w312w413w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0xfdd655b8…bf89
0x34b655…2a6f
6 touches
3 conflicts
0x03c2acba…6f0f
0x34b655…2a6f
4 touches
1 conflict
0x32646adf…e05d
0x34b655…2a6f
4 touches
1 conflict
0x3d4c0233…20a5
0x34b655…2a6f
4 touches
1 conflict
0x4c188934…158e
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity