← previous blocknext block →recent activity
Analyzing
Block #92,288,064
11 transactions · 7 stateful · 2026-08-01 19:39:42 UTC
Parallelism
64/100
Blocked
43%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #92,288,064 · 11 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
7w08w19w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xe0e2323d…8e35
0x34b655…2a6f
6 touches
3 conflicts
0x75e3e885…c593
0x34b655…2a6f
6 touches
3 conflicts
0xa76e0cd5…e3c5
0x34b655…2a6f
6 touches
3 conflicts
0xa82b709f…de9f
0x34b655…2a6f
6 touches
3 conflicts
0xd1dd2e56…48f2
0x34b655…2a6f
6 touches
3 conflicts
0x6fbc2e5a…e69c
0x34b655…2a6f
4 touches
1 conflict
0x890a06f3…8539
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity