← previous blocknext block →recent activity
Analyzing
Block #86,630,293
22 transactions · 18 stateful · 2026-07-09 13:16:03 UTC
Parallelism
68/100
Blocked
33%
Avg conflicts / tx
0.82
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,630,293 · 22 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w011w112w213w317w418w520w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0xa08f40b2…9a93
0x34b655…2a6f
8 touches
6 conflicts
0x1321736a…43e3
0x34b655…2a6f
4 touches
1 conflict
0x140eb1ca…bc07
0x34b655…2a6f
4 touches
1 conflict
0x16a8cd0c…27bd
0x34b655…2a6f
4 touches
1 conflict
0x25191452…d2ed
0x34b655…2a6f
4 touches
1 conflict
0x2533f477…a43b
0x34b655…2a6f
4 touches
1 conflict
0x410b84ab…1dbc
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
15 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity