← previous blocknext block →recent activity
Analyzing
Block #94,717,307
21 transactions · 17 stateful · 2026-08-10 07:35:34 UTC
Parallelism
76/100
Blocked
41%
Avg conflicts / tx
0.67
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #94,717,307 · 21 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
4w05w16w27w39w010w114w417w220w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x379dc435…6616
0x34b655…2a6f
10 touches
10 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xf761c0bf…8598
0x34b655…2a6f
4 touches
1 conflict
0x461f7d91…c43b
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x97d5efed…1aa4
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
10 conflicts on slot 0x379dc43545…336616
Audit this contract →
← previous block·next block →recent activity