← previous blocknext block →recent activity
Analyzing
Block #94,807,790
44 transactions · 40 stateful · 2026-08-10 15:12:11 UTC
Parallelism
61/100
Blocked
60%
Avg conflicts / tx
2.98
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #94,807,790 · 44 txs across 17 waves · depth 17
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w08w29w110w312w413w514w515w616w723w824w925w1026w1127w1231w1141w1443w16
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xec7d120d…7084
0x34b655…2a6f
18 touches
36 conflicts
0xca841faa…486a
0x34b655…2a6f
14 touches
21 conflicts
0xf0d45ffd…89cf
0x34b655…2a6f
14 touches
21 conflicts
0x95c47f03…f1bb
0x34b655…2a6f
10 touches
10 conflicts
0xabd0bcfc…64e2
0x34b655…2a6f
10 touches
10 conflicts
0xac2a0273…721b
0x34b655…2a6f
10 touches
10 conflicts
0x0a57a2b8…3cdd
0x34b655…2a6f
8 touches
6 conflicts
0x428b6e5b…8909
0x34b655…2a6f
8 touches
6 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
36 conflicts on slot 0xec7d120df9…5d7084
Audit this contract →
← previous block·next block →recent activity