← previous blocknext block →recent activity
Analyzing
Block #92,564,190
18 transactions · 17 stateful · 2026-08-02 18:48:23 UTC
Parallelism
72/100
Blocked
35%
Avg conflicts / tx
0.39
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #92,564,190 · 18 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w17w08w09w111w114w215w316w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6b778857…f22f
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x3e505a15…70f8
0x34b655…2a6f
4 touches
1 conflict
0x3eacdae2…6436
0x34b655…2a6f
4 touches
1 conflict
0x3efad0b5…b0a8
0x34b655…2a6f
4 touches
1 conflict
0x3efad0b5…b0a9
0x34b655…2a6f
4 touches
1 conflict
0x42fe28d1…478c
0x34b655…2a6f
4 touches
1 conflict
0x454cdf57…aebc
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 0x6b77885710…95f22f
Audit this contract →
← previous block·next block →recent activity