← previous blocknext block →recent activity
Analyzing
Block #86,102,101
18 transactions · 15 stateful · 2026-07-07 02:26:05 UTC
Parallelism
72/100
Blocked
40%
Avg conflicts / tx
0.67
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,102,101 · 18 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
1w03w04w15w06w19w215w116w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc4cb048e…7562
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0x1cefae97…7f45
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x2ed98d3b…78ef
0x34b655…2a6f
4 touches
1 conflict
0x43497f01…25d0
0x34b655…2a6f
4 touches
1 conflict
0x6d972fb2…46b7
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 0xc4cb048ec1…6f7562
Audit this contract →
← previous block·next block →recent activity