← previous blocknext block →recent activity
Analyzing
Block #86,320,243
17 transactions · 14 stateful · 2026-07-08 02:42:38 UTC
Parallelism
82/100
Blocked
21%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,320,243 · 17 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
1w02w03w113w014w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x34959a18…39ea
0x34b655…2a6f
6 touches
3 conflicts
0xfa1a8731…ca65
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xffb8950c…23c6
0x34b655…2a6f
6 touches
3 conflicts
0xd4726587…6289
0x34b655…2a6f
5 touches
3 conflicts
0x3e505a15…70f8
0x34b655…2a6f
4 touches
1 conflict
0x6f1a10f8…5a04
0x34b655…2a6f
4 touches
1 conflict
0x7a2fc410…c088
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
3 conflicts on slot 0x34959a18b5…2f39ea
Audit this contract →
← previous block·next block →recent activity