← previous blocknext block →recent activity
Analyzing
Block #87,616,793
19 transactions · 14 stateful · 2026-07-14 03:12:47 UTC
Parallelism
74/100
Blocked
36%
Avg conflicts / tx
0.58
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,616,793 · 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
2w03w17w18w29w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x38d36864…2cb0
0x34b655…2a6f
8 touches
6 conflicts
0xca3f1796…927c
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x3368cd86…62f9
0x34b655…2a6f
6 touches
3 conflicts
0x59a5e379…ad8e
0x34b655…2a6f
4 touches
1 conflict
0x59a5e379…ad8f
0x34b655…2a6f
4 touches
1 conflict
0x5c881ba4…0f46
0x34b655…2a6f
4 touches
1 conflict
0x79e5df76…64ee
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 0x38d36864ff…6b2cb0
Audit this contract →
← previous block·next block →recent activity