← previous blocknext block →recent activity
Analyzing
Block #92,970,411
13 transactions · 13 stateful · 2026-08-04 04:53:11 UTC
Parallelism
69/100
Blocked
23%
Avg conflicts / tx
0.31
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #92,970,411 · 13 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
6w07w111w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x94f2c3b4…4ef6
0x34b655…2a6f
6 touches
3 conflicts
0x120847e2…98c2
0x34b655…2a6f
4 touches
1 conflict
0x16d6e3aa…d3a6
0x34b655…2a6f
4 touches
1 conflict
0x1a4e1987…6337
0x34b655…2a6f
4 touches
1 conflict
0x1af644dc…0822
0x34b655…2a6f
4 touches
1 conflict
0x286711a5…b3bf
0x34b655…2a6f
4 touches
1 conflict
0x57be321f…fecc
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
3 conflicts on slot 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity