← previous blocknext block →recent activity
Analyzing
Block #94,305,429
13 transactions · 13 stateful · 2026-08-08 20:55:18 UTC
Parallelism
85/100
Blocked
23%
Avg conflicts / tx
0.31
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #94,305,429 · 13 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
3w04w05w06w07w18w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x781f7a3d…c105
0x34b655…2a6f
4 touches
1 conflict
0xc6b604e6…5152
0x34b655…2a6f
4 touches
1 conflict
0x2a9e9bd1…5368
0x2a68ba…90c5
4 touches
1 conflict
0x6d1b72ee…6b78
0x34b655…2a6f
4 touches
1 conflict
0x6f600d51…ffed
0x34b655…2a6f
4 touches
1 conflict
0x2fdf4ed3…7dce
0xa6afd3…d132
3 touches
1 conflict
0x34d95d94…3a16
0x34b655…2a6f
2 touches
0 conflicts
0x3b2c8363…a429
0x34b655…2a6f
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 0x781f7a3d0c…b6c105
Audit this contract →
← previous block·next block →recent activity