← previous blocknext block →recent activity
Analyzing
Block #94,792,616
21 transactions · 20 stateful · 2026-08-10 13:55:51 UTC
Parallelism
67/100
Blocked
40%
Avg conflicts / tx
0.9
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #94,792,616 · 21 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w07w28w310w411w112w517w018w119w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2840c278…bbc7
0x34b655…2a6f
8 touches
6 conflicts
0x08330b36…ae29
0x34b655…2a6f
6 touches
3 conflicts
0x43fd3667…094b
0x34b655…2a6f
6 touches
3 conflicts
0x584cb6c4…cdde
0x34b655…2a6f
6 touches
3 conflicts
0x973606e8…cb0f
0x34b655…2a6f
6 touches
3 conflicts
0xb514ce62…3397
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x57b02276…db3f
0x34b655…2a6f
4 touches
1 conflict
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 0x2840c278a3…01bbc7
Audit this contract →
← previous block·next block →recent activity