← previous blocknext block →recent activity
Analyzing
Block #94,198,772
9 transactions · 9 stateful · 2026-08-08 11:54:54 UTC
Parallelism
67/100
Blocked
44%
Avg conflicts / tx
0.67
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #94,198,772 · 9 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w28w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x53f393fa…00b9
0x34b655…2a6f
6 touches
3 conflicts
0xad3e66be…dccc
0xc8689a…ee79
4 touches
1 conflict
0x9fd37234…2731
0x34b655…2a6f
4 touches
1 conflict
0xa8793b16…522e
0x34b655…2a6f
4 touches
1 conflict
0xbbf81489…9ad9
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x0087ca84…0b18
0x34b655…2a6f
4 touches
1 conflict
0x04994ed2…9032
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 0x53f393fafd…2a00b9
Audit this contract →
← previous block·next block →recent activity