← previous blocknext block →recent activity
Analyzing
Block #94,225,805
20 transactions · 19 stateful · 2026-08-08 14:11:46 UTC
Parallelism
80/100
Blocked
37%
Avg conflicts / tx
0.7
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #94,225,805 · 20 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
1w02w14w05w06w17w28w39w010w111w219w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfd19acf7…5423
0x34b655…2a6f
8 touches
6 conflicts
0x0778475b…bd75
0x2a68ba…90c5
6 touches
3 conflicts
0xa9a9d0e0…4087
0x34b655…2a6f
6 touches
3 conflicts
0xf3383813…4a0c
0x34b655…2a6f
6 touches
3 conflicts
0xf2f4727d…cdb7
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xb5d52596…99d8
0x065c9d…c394
5 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 0xfd19acf719…f75423
Audit this contract →
← previous block·next block →recent activity