← previous blocknext block →recent activity
Analyzing
Block #92,966,794
7 transactions · 6 stateful · 2026-08-04 04:34:59 UTC
Parallelism
71/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #92,966,794 · 7 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
2w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5da59c2b…d7b2
0x34b655…2a6f
4 touches
1 conflict
0xf9874e36…beed
0x34b655…2a6f
4 touches
1 conflict
0x1de366f5…69a3
0x34b655…2a6f
4 touches
1 conflict
0x91cdfdeb…7feb
0x34b655…2a6f
4 touches
1 conflict
0x41fa1a39…d1f8
0x34b655…2a6f
2 touches
0 conflicts
0x43cb76fb…c4e3
0x34b655…2a6f
2 touches
0 conflicts
0x704957ad…da26
0x34b655…2a6f
2 touches
0 conflicts
0x9375a764…dca1
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 0x5da59c2b2f…b6d7b2
Audit this contract →
← previous block·next block →recent activity