← previous blocknext block →recent activity
Analyzing
Block #92,870,461
17 transactions · 16 stateful · 2026-08-03 20:30:20 UTC
Parallelism
59/100
Blocked
44%
Avg conflicts / tx
1.18
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #92,870,461 · 17 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
1w03w14w26w38w09w111w412w513w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x439484d9…2f92
0x34b655…2a6f
4 touches
1 conflict
0x5891e4a8…99d1
0x34b655…2a6f
4 touches
1 conflict
0x5d832806…eb38
0x34b655…2a6f
4 touches
1 conflict
0x6784a12f…fca5
0x34b655…2a6f
4 touches
1 conflict
0x725d28d9…d91f
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
10 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity