← previous blocknext block →recent activity
Analyzing
Block #87,786,613
15 transactions · 14 stateful · 2026-07-14 22:08:43 UTC
Parallelism
73/100
Blocked
21%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,786,613 · 15 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
2w05w07w113w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3f85f288…7c97
0x34b655…2a6f
6 touches
3 conflicts
0x5251466a…41d6
0x34b655…2a6f
4 touches
1 conflict
0x587911c7…9e01
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x7d248840…6b0f
0x34b655…2a6f
4 touches
1 conflict
0xf3fbc9b8…ab58
0x34b655…2a6f
4 touches
1 conflict
0x09cd9841…d332
0x34b655…2a6f
2 touches
0 conflicts
0x0b826166…904e
0x34b655…2a6f
2 touches
0 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
3 conflicts on slot 0x3f85f288f7…917c97
Audit this contract →
← previous block·next block →recent activity