← previous blocknext block →recent activity
Analyzing
Block #86,451,083
17 transactions · 17 stateful · 2026-07-08 17:16:40 UTC
Parallelism
76/100
Blocked
18%
Avg conflicts / tx
0.18
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,451,083 · 17 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w010w113w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb624d2ea…8c87
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x47861365…d699
0x34b655…2a6f
4 touches
1 conflict
0x04105a34…6eea
0x34b655…2a6f
2 touches
0 conflicts
0x00000000…0004
0x5afd3e…7620
2 touches
0 conflicts
0x0cf1a8c2…8532
0x5afd3e…7620
2 touches
0 conflicts
0x5437bdf2…bdba
0x5afd3e…7620
2 touches
0 conflicts
0x00000000…0006
0x60bb42…87ea
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 0xb624d2eae3…2b8c87
Audit this contract →
← previous block·next block →recent activity