← previous blocknext block →recent activity
Analyzing
Block #94,812,417
21 transactions · 21 stateful · 2026-08-10 15:35:28 UTC
Parallelism
67/100
Blocked
43%
Avg conflicts / tx
1.33
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #94,812,417 · 21 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w05w16w27w08w19w211w012w313w415w516w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x734ee320…caae
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xfecb18c0…01ed
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x47c24931…9b04
0x34b655…2a6f
6 touches
3 conflicts
0x7083b83e…33da
0x34b655…2a6f
6 touches
3 conflicts
0xbbedfd60…0fec
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
15 conflicts on slot 0x734ee32053…cecaae
Audit this contract →
← previous block·next block →recent activity