← previous blocknext block →recent activity
Analyzing
Block #87,623,860
19 transactions · 14 stateful · 2026-07-14 04:00:01 UTC
Parallelism
74/100
Blocked
43%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,623,860 · 19 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
2w03w16w27w38w411w418w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x99c46e97…c1b2
0x34b655…2a6f
8 touches
6 conflicts
0x4c188934…158e
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x1c8b4f85…d07d
0x34b655…2a6f
4 touches
1 conflict
0x2328941c…84d3
0x34b655…2a6f
4 touches
1 conflict
0x3cb8c8c3…22f4
0x34b655…2a6f
4 touches
1 conflict
0x43bc2389…898f
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 0x99c46e97a0…cac1b2
Audit this contract →
← previous block·next block →recent activity