← previous blocknext block →recent activity
Analyzing
Block #86,741,225
25 transactions · 21 stateful · 2026-07-10 01:38:09 UTC
Parallelism
84/100
Blocked
48%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,741,225 · 25 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
1w02w03w15w16w07w18w011w213w214w015w218w119w220w324w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00bac013…a28c
0xfd44b3…00d1
6 touches
3 conflicts
0x05ca4d57…2eed
0x34b655…2a6f
6 touches
3 conflicts
0x43e15ca4…039d
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x0d622e34…0000
0x681e90…ae09
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
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: 0xfd44b351…7f00d1
3 conflicts on slot 0x00bac0131a…bba28c
Audit this contract →
← previous block·next block →recent activity