← previous blocknext block →recent activity
Analyzing
Block #94,948,804
23 transactions · 22 stateful · 2026-08-11 03:01:29 UTC
Parallelism
78/100
Blocked
36%
Avg conflicts / tx
0.48
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #94,948,804 · 23 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
3w05w06w17w08w110w211w312w013w114w116w422w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa3a621f8…75a2
0x34b655…2a6f
6 touches
3 conflicts
0x00a19519…11c6
0x34b655…2a6f
4 touches
1 conflict
0x08b68583…01a1
0x34b655…2a6f
4 touches
1 conflict
0x4a882081…c5e0
0x34b655…2a6f
4 touches
1 conflict
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x7ced4002…dd55
0x34b655…2a6f
4 touches
1 conflict
0xf219f7cf…7379
0xa6afd3…d132
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
3 conflicts on slot 0xa3a621f8f3…6975a2
Audit this contract →
← previous block·next block →recent activity