← previous blocknext block →recent activity
Analyzing
Block #92,481,951
17 transactions · 17 stateful · 2026-08-02 11:54:49 UTC
Parallelism
88/100
Blocked
6%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #92,481,951 · 17 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
3w07w09w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x35a9f06c…7689
0x34b655…2a6f
4 touches
1 conflict
0x5fe7e126…6dd2
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xea1b8c07…b969
0x34b655…2a6f
4 touches
1 conflict
0x40970e69…da50
0x2b46c0…1669
2 touches
0 conflicts
0x064bb149…79fd
0x34b655…2a6f
2 touches
0 conflicts
0x0ff91e5e…6434
0x34b655…2a6f
2 touches
0 conflicts
0x11db128b…1153
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 0x35a9f06ccf…e37689
Audit this contract →
← previous block·next block →recent activity