← previous blocknext block →recent activity
Analyzing
Block #94,982,528
19 transactions · 16 stateful · 2026-08-11 05:51:05 UTC
Parallelism
74/100
Blocked
56%
Avg conflicts / tx
0.95
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #94,982,528 · 19 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w16w27w08w19w210w314w015w117w318w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1a5d321d…a474
0x34b655…2a6f
10 touches
10 conflicts
0xa1087a5c…66c4
0x754704…b603
8 touches
6 conflicts
0x11b69a7e…334e
0x01bff4…1071
8 touches
6 conflicts
0x9fd372a1…a959
0x34b655…2a6f
8 touches
6 conflicts
0x0400063e…200e
0x851145…3f07
6 touches
3 conflicts
0x002fed35…79fa
0x2a68ba…90c5
6 touches
3 conflicts
0x27f75f20…525c
0x34b655…2a6f
6 touches
3 conflicts
0x60d9e993…c0b8
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
10 conflicts on slot 0x1a5d321d5d…0da474
Audit this contract →
← previous block·next block →recent activity