← previous blocknext block →recent activity
Analyzing
Block #92,859,168
13 transactions · 13 stateful · 2026-08-03 19:33:31 UTC
Parallelism
69/100
Blocked
23%
Avg conflicts / tx
0.46
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #92,859,168 · 13 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x542ff3d0…3fa7
0x34b655…2a6f
6 touches
3 conflicts
0x84d6407e…6fb2
0x34b655…2a6f
6 touches
3 conflicts
0x897b8488…bebe
0x34b655…2a6f
6 touches
3 conflicts
0x40ee7a94…d6a8
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641f
0x34b655…2a6f
6 touches
3 conflicts
0x4e50038e…6e29
0x34b655…2a6f
6 touches
3 conflicts
0x5efd7300…d8a5
0x34b655…2a6f
4 touches
1 conflict
0x9da86eb9…0c75
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
3 conflicts on slot 0x542ff3d046…773fa7
Audit this contract →
← previous block·next block →recent activity