← previous blocknext block →recent activity
Analyzing
Block #86,768,528
22 transactions · 20 stateful · 2026-07-10 04:40:35 UTC
Parallelism
91/100
Blocked
15%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,768,528 · 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
2w03w14w05w16w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc6c51e22…fbfb
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x04fdea…47d7
4 touches
1 conflict
0xfaef08b1…0696
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
2 touches
0 conflicts
0x119694b6…b8dc
0x34b655…2a6f
2 touches
0 conflicts
0x8391fb68…4c83
0x34b655…2a6f
2 touches
0 conflicts
0xc2ebcc0c…2261
0x34b655…2a6f
2 touches
0 conflicts
0xcfb9b777…5e1b
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 0xc6c51e2202…1afbfb
Audit this contract →
← previous block·next block →recent activity