← previous blocknext block →recent activity
Analyzing
Block #86,934,447
14 transactions · 10 stateful · 2026-07-10 23:09:38 UTC
Parallelism
79/100
Blocked
20%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,934,447 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf1e0de4d…eb7f
0x34b655…2a6f
4 touches
1 conflict
0x1dddd7ef…8f05
0x34b655…2a6f
4 touches
1 conflict
0xa08f40b2…9a93
0x34b655…2a6f
4 touches
1 conflict
0xaca95d16…63e3
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x93459aa0…fb74
0x34b655…2a6f
2 touches
0 conflicts
0xaf98736d…8142
0x34b655…2a6f
2 touches
0 conflicts
0xe246730f…760d
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
1 conflict on slot 0xf1e0de4d7d…c0eb7f
Audit this contract →
← previous block·next block →recent activity