← previous blocknext block →recent activity
Analyzing
Block #86,133,030
12 transactions · 11 stateful · 2026-07-07 05:52:34 UTC
Parallelism
83/100
Blocked
27%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,133,030 · 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
1w02w03w16w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x745a7fd6…5fea
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x0a6f5e37…6c3c
0x34b655…2a6f
4 touches
1 conflict
0x15c9b5bf…f732
0x34b655…2a6f
2 touches
0 conflicts
0x196c2058…bb2e
0x34b655…2a6f
2 touches
0 conflicts
0x24b597d0…6ce1
0x34b655…2a6f
2 touches
0 conflicts
0x6b25c3c6…bf3f
0x34b655…2a6f
2 touches
0 conflicts
0x737acb78…fce8
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 0x745a7fd6fd…595fea
Audit this contract →
← previous block·next block →recent activity