← previous blocknext block →recent activity
Analyzing
Block #92,419,960
12 transactions · 11 stateful · 2026-08-02 06:42:59 UTC
Parallelism
83/100
Blocked
9%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #92,419,960 · 12 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
2w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9a8482cc…8bee
0x34b655…2a6f
4 touches
1 conflict
0xf67dab35…5381
0x34b655…2a6f
4 touches
1 conflict
0x4efae872…6aa8
0x34b655…2a6f
4 touches
1 conflict
0x09b4c363…d79e
0x34b655…2a6f
2 touches
0 conflicts
0x267fe70d…159e
0x34b655…2a6f
2 touches
0 conflicts
0x34b042d4…3f45
0x34b655…2a6f
2 touches
0 conflicts
0x34b042d4…3f46
0x34b655…2a6f
2 touches
0 conflicts
0x35c29640…8779
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 0x9a8482cc51…b88bee
Audit this contract →
← previous block·next block →recent activity