← previous blocknext block →recent activity
Analyzing
Block #94,791,716
50 transactions · 40 stateful · 2026-08-10 13:51:19 UTC
Parallelism
70/100
Blocked
75%
Avg conflicts / tx
2.6
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #94,791,716 · 50 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
2w03w14w26w07w18w09w210w111w312w213w314w415w516w617w718w519w626w727w835w1236w1338w1439w140w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
16 touches
28 conflicts
0xec7d120d…7084
0x34b655…2a6f
16 touches
28 conflicts
0x0a57a2b8…3cdd
0x34b655…2a6f
12 touches
15 conflicts
0x94bb14fe…8f47
0x34b655…2a6f
10 touches
10 conflicts
0xdc2cf997…8a8f
0x34b655…2a6f
10 touches
10 conflicts
0x2840c278…bbc7
0x34b655…2a6f
10 touches
10 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
8 touches
6 conflicts
0xa279b18d…63bc
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
28 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity