← previous blocknext block →recent activity
Analyzing
Block #87,419,217
17 transactions · 13 stateful · 2026-07-13 05:10:43 UTC
Parallelism
71/100
Blocked
38%
Avg conflicts / tx
0.59
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,419,217 · 17 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
2w03w04w15w27w18w39w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc6fabe47…654e
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xb41b50ff…81b1
0x34b655…2a6f
6 touches
3 conflicts
0x169daa40…3f75
0x34b655…2a6f
6 touches
3 conflicts
0x59a5e379…ad8e
0x34b655…2a6f
4 touches
1 conflict
0x59a5e379…ad8f
0x34b655…2a6f
4 touches
1 conflict
0x60e95cf4…3f88
0x34b655…2a6f
4 touches
1 conflict
0x73871297…b08d
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
3 conflicts on slot 0xc6fabe47a4…9e654e
Audit this contract →
← previous block·next block →recent activity