← previous blocknext block →recent activity
Analyzing
Block #86,814,887
12 transactions · 12 stateful · 2026-07-10 09:50:09 UTC
Parallelism
83/100
Blocked
17%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,814,887 · 12 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w110w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x33c7a9e0…4810
0x34b655…2a6f
4 touches
1 conflict
0xf464e900…f28d
0x34b655…2a6f
4 touches
1 conflict
0x8344e533…436c
0x34b655…2a6f
4 touches
1 conflict
0xf464e900…f28c
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xd95edc7f…db92
0x34b655…2a6f
4 touches
1 conflict
0x206d244a…9a41
0x34b655…2a6f
3 touches
1 conflict
0xb54c8ced…5b8c
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 0x33c7a9e0fd…4e4810
Audit this contract →
← previous block·next block →recent activity