← previous blocknext block →recent activity
Analyzing
Block #92,973,819
10 transactions · 8 stateful · 2026-08-04 05:10:19 UTC
Parallelism
80/100
Blocked
13%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #92,973,819 · 10 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
0xa56e54d0…2d39
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x10d1ee76…de9e
0x34b655…2a6f
2 touches
0 conflicts
0x215a6da4…0e86
0x34b655…2a6f
2 touches
0 conflicts
0x26e64aea…de52
0x34b655…2a6f
2 touches
0 conflicts
0x28fe74b6…efa9
0x34b655…2a6f
2 touches
0 conflicts
0x47ef34f4…78a7
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 0xa56e54d018…f82d39
Audit this contract →
← previous block·next block →recent activity