← previous blocknext block →recent activity
Analyzing
Block #94,665,904
56 transactions · 55 stateful · 2026-08-10 03:17:02 UTC
Parallelism
96/100
Blocked
4%
Avg conflicts / tx
0.04
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #94,665,904 · 56 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
48w049w152w053w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb42343e0…2a28
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x3a921be0…779c
0x2a68ba…90c5
2 touches
0 conflicts
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x06ce5d4b…c122
0x2b46c0…1669
2 touches
0 conflicts
0x213ee207…a151
0x2b46c0…1669
2 touches
0 conflicts
0x46279ae7…20dd
0x2b46c0…1669
2 touches
0 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
1 conflict on slot 0xb42343e036…3a2a28
Audit this contract →
← previous block·next block →recent activity