← previous blocknext block →recent activity
Analyzing
Block #92,456,246
14 transactions · 13 stateful · 2026-08-02 09:45:28 UTC
Parallelism
86/100
Blocked
8%
Avg conflicts / tx
0.07
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #92,456,246 · 14 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
4w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5e0b8bbe…377b
0x34b655…2a6f
4 touches
1 conflict
0x4755fafb…859b
0x34b655…2a6f
4 touches
1 conflict
0x68c07cb9…ae14
0x34b655…2a6f
4 touches
1 conflict
0xad3e66be…dccc
0xc8689a…ee79
4 touches
1 conflict
0x4a5956ef…e226
0x34b655…2a6f
4 touches
1 conflict
0x064bb149…79fd
0x34b655…2a6f
2 touches
0 conflicts
0x0f8965bb…e238
0x34b655…2a6f
2 touches
0 conflicts
0x2328941c…84d3
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 0x5e0b8bbea5…e9377b
Audit this contract →
← previous block·next block →recent activity