← previous blocknext block →recent activity
Analyzing
Block #86,788,584
22 transactions · 17 stateful · 2026-07-10 06:54:26 UTC
Parallelism
86/100
Blocked
24%
Avg conflicts / tx
0.18
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,788,584 · 22 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
1w02w14w27w08w19w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca496ab2…26ce
0x34b655…2a6f
4 touches
1 conflict
0x90e113f8…c8f9
0xc8689a…ee79
4 touches
1 conflict
0xfadc118d…5d64
0x34b655…2a6f
4 touches
1 conflict
0xfa2527aa…9dd5
0x34b655…2a6f
4 touches
1 conflict
0xdcae00a6…c017
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x119694b6…b8dc
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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
1 conflict on slot 0xca496ab29e…2826ce
Audit this contract →
← previous block·next block →recent activity