← previous blocknext block →recent activity
Analyzing
Block #92,471,799
16 transactions · 16 stateful · 2026-08-02 11:03:44 UTC
Parallelism
69/100
Blocked
38%
Avg conflicts / tx
0.56
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #92,471,799 · 16 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
3w04w15w26w38w49w213w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x388b50b4…a2b4
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xbdc80bf7…e947
0x34b655…2a6f
6 touches
3 conflicts
0x248e43aa…7287
0x34b655…2a6f
4 touches
1 conflict
0x3adf6cd7…6f2c
0x34b655…2a6f
4 touches
1 conflict
0x816c7d6d…98ea
0x34b655…2a6f
4 touches
1 conflict
0x816c7d6d…98eb
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 0x388b50b44a…05a2b4
Audit this contract →
← previous block·next block →recent activity