← previous blocknext block →recent activity
Analyzing
Block #86,323,690
22 transactions · 16 stateful · 2026-07-08 03:05:40 UTC
Parallelism
91/100
Blocked
31%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,323,690 · 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
1w04w07w08w09w110w111w114w115w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x43e3decb…be40
0x34b655…2a6f
4 touches
1 conflict
0x17606ba6…1b6e
0x754704…b603
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x6b405d1c…29a4
0x851145…3f07
4 touches
1 conflict
0x11aec45e…bef4
0xd32edf…ff58
3 touches
1 conflict
0x00000000…0004
0x5afd3e…7620
2 touches
0 conflicts
0xb1e94816…cc04
0x5afd3e…7620
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 0x43e3decb93…7dbe40
Audit this contract →
← previous block·next block →recent activity