← previous blocknext block →recent activity
Analyzing
Block #94,758,908
29 transactions · 20 stateful · 2026-08-10 11:06:18 UTC
Parallelism
83/100
Blocked
45%
Avg conflicts / tx
0.55
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #94,758,908 · 29 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w010w114w215w016w117w018w120w321w223w325w426w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4eb691ce…350c
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x92d610a6…9a40
0x2a68ba…90c5
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x97940d54…7640
0xd32edf…ff58
5 touches
3 conflicts
0xd2d4f849…51c8
0x065c9d…c394
5 touches
3 conflicts
0x1ced2a7d…5c90
0x34b655…2a6f
4 touches
1 conflict
0x3643741b…109c
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
6 conflicts on slot 0x4eb691cec6…a4350c
Audit this contract →
← previous block·next block →recent activity