← previous blocknext block →recent activity
Analyzing
Block #86,193,567
22 transactions · 15 stateful · 2026-07-07 12:36:41 UTC
Parallelism
91/100
Blocked
13%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,193,567 · 22 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
7w013w017w120w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x167de262…f61f
0x34b655…2a6f
4 touches
1 conflict
0xf8f3c378…789a
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xcc6e2e88…6569
0x34b655…2a6f
4 touches
1 conflict
0x68c07cb9…ae14
0x34b655…2a6f
4 touches
1 conflict
0xad21af90…5fb2
0xd32edf…ff58
3 touches
1 conflict
0x46cb45de…a568
0x188d58…ea8e
2 touches
0 conflicts
0x46cb45de…a566
0x188d58…ea8e
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 0x167de262c8…3ef61f
Audit this contract →
← previous block·next block →recent activity