← previous blocknext block →recent activity
Analyzing
Block #94,484,109
53 transactions · 44 stateful · 2026-08-09 12:02:40 UTC
Parallelism
72/100
Blocked
73%
Avg conflicts / tx
2.36
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #94,484,109 · 53 txs across 15 waves · depth 15
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w16w27w09w110w011w112w215w320w421w532w635w137w139w841w243w345w246w147w948w1049w1151w1352w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac2a0273…721b
0x34b655…2a6f
20 touches
45 conflicts
0x737acb78…fce8
0x34b655…2a6f
16 touches
28 conflicts
0xcc351d6d…256b
0x34b655…2a6f
16 touches
28 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0xf4f9cac7…fd98
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x95c47f03…f1bb
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
45 conflicts on slot 0xac2a02739b…81721b
Audit this contract →
← previous block·next block →recent activity