← previous blocknext block →recent activity
Analyzing
Block #94,810,950
16 transactions · 14 stateful · 2026-08-10 15:28:05 UTC
Parallelism
69/100
Blocked
43%
Avg conflicts / tx
0.75
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #94,810,950 · 16 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
1w02w13w05w18w09w112w214w315w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa6b89ebb…a66e
0x34b655…2a6f
10 touches
10 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x625d993f…3510
0x34b655…2a6f
4 touches
1 conflict
0x68c07cb9…ae14
0x34b655…2a6f
4 touches
1 conflict
0x7d734d5f…c6df
0x34b655…2a6f
4 touches
1 conflict
0x8b76e9f2…54ee
0x34b655…2a6f
4 touches
1 conflict
0x9ae859db…2d84
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
10 conflicts on slot 0xa6b89ebbaf…5fa66e
Audit this contract →
← previous block·next block →recent activity