← previous blocknext block →recent activity
Analyzing
Block #86,884,503
22 transactions · 19 stateful · 2026-07-10 17:35:48 UTC
Parallelism
82/100
Blocked
32%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,884,503 · 22 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
1w03w08w09w111w113w114w220w221w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb06917e8…6985
0x34b655…2a6f
8 touches
6 conflicts
0x202c03eb…cf33
0xa6afd3…d132
6 touches
3 conflicts
0xb0446875…2b96
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x36810ff7…1728
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x77722039…2e5c
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
6 conflicts on slot 0xb06917e887…5e6985
Audit this contract →
← previous block·next block →recent activity