← previous blocknext block →recent activity
Analyzing
Block #94,667,395
17 transactions · 17 stateful · 2026-08-10 03:24:32 UTC
Parallelism
65/100
Blocked
41%
Avg conflicts / tx
0.88
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #94,667,395 · 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
2w03w14w07w18w09w211w314w315w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6459805c…615d
0x34b655…2a6f
8 touches
6 conflicts
0x017f6cf2…ca6e
0x34b655…2a6f
6 touches
3 conflicts
0x120847e2…98c2
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x53699236…fede
0x34b655…2a6f
6 touches
3 conflicts
0x548145a9…cfce
0x34b655…2a6f
6 touches
3 conflicts
0x5f447bf3…57c7
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 0x6459805cc4…18615d
Audit this contract →
← previous block·next block →recent activity