← previous blocknext block →recent activity
Analyzing
Block #86,103,206
13 transactions · 9 stateful · 2026-07-07 02:33:25 UTC
Parallelism
85/100
Blocked
22%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,103,206 · 13 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
2w03w111w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5eb3c33…0e3a
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe4af4c87…9964
0x34b655…2a6f
4 touches
1 conflict
0xd991a254…0f62
0x1001ff…1001
2 touches
0 conflicts
0x00000000…0000
0x276664…5732
2 touches
0 conflicts
0x4c619b7d…f4fa
0x34b655…2a6f
2 touches
0 conflicts
0x75bebd36…d14f
0x34b655…2a6f
2 touches
0 conflicts
0x8a7af3fd…72a7
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 0xe5eb3c3335…0c0e3a
Audit this contract →
← previous block·next block →recent activity