← previous blocknext block →recent activity
Analyzing
Block #92,471,913
13 transactions · 10 stateful · 2026-08-02 11:04:18 UTC
Parallelism
77/100
Blocked
20%
Avg conflicts / tx
0.23
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #92,471,913 · 13 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w18w09w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8f63f383…6eda
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x388b50b4…a2b4
0x34b655…2a6f
4 touches
1 conflict
0x29c1a140…099f
0x34b655…2a6f
4 touches
1 conflict
0x8934c300…b5aa
0x34b655…2a6f
2 touches
0 conflicts
0x9ad82ccb…b08b
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 0x8f63f383d9…ff6eda
Audit this contract →
← previous block·next block →recent activity