← previous blocknext block →recent activity
Analyzing
Block #94,050,457
12 transactions · 12 stateful · 2026-08-07 23:25:41 UTC
Parallelism
67/100
Blocked
33%
Avg conflicts / tx
0.42
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #94,050,457 · 12 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w06w19w110w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x103be197…826c
0xa6afd3…d132
4 touches
1 conflict
0xa45116ed…5331
0x34b655…2a6f
4 touches
1 conflict
0xa8433624…8969
0x34b655…2a6f
4 touches
1 conflict
0xd4702f73…926c
0x34b655…2a6f
4 touches
1 conflict
0xebac0f82…a49c
0x34b655…2a6f
4 touches
1 conflict
0xecf5834b…70b8
0x34b655…2a6f
4 touches
1 conflict
0xf4a27876…b09c
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
3 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity