← previous blocknext block →recent activity
Analyzing
Block #93,136,147
17 transactions · 14 stateful · 2026-08-04 18:48:10 UTC
Parallelism
65/100
Blocked
36%
Avg conflicts / tx
0.71
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #93,136,147 · 17 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w19w210w311w414w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xef3f5637…f47c
0x34b655…2a6f
8 touches
6 conflicts
0xdfb97a89…abc8
0x34b655…2a6f
8 touches
6 conflicts
0xfd42a6b9…4c81
0x34b655…2a6f
6 touches
3 conflicts
0xa60eabc0…9f8c
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity