← previous blocknext block →recent activity
Analyzing
Block #94,974,327
21 transactions · 18 stateful · 2026-08-11 05:09:50 UTC
Parallelism
67/100
Blocked
44%
Avg conflicts / tx
1.1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #94,974,327 · 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
6w07w19w010w111w212w313w414w515w617w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x11b69a7e…334e
0x01bff4…1071
14 touches
21 conflicts
0xa1087a5c…66c4
0x754704…b603
14 touches
21 conflicts
0x07b86c51…cdae
0x2a68ba…90c5
8 touches
6 conflicts
0x8d685458…029e
0x851145…3f07
8 touches
6 conflicts
0xf60c777f…6d0f
0x851145…3f07
6 touches
3 conflicts
0x002fed35…79fa
0x2a68ba…90c5
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xcda18b0b…6a4c
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: 0x01bff417…bc1071
21 conflicts on slot 0x11b69a7ea1…83334e
Audit this contract →
← previous block·next block →recent activity