← previous blocknext block →recent activity
Analyzing
Block #94,317,708
13 transactions · 12 stateful · 2026-08-08 21:57:37 UTC
Parallelism
85/100
Blocked
25%
Avg conflicts / tx
0.31
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #94,317,708 · 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
1w04w05w06w17w111w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdd0f9852…647b
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x1f90c45d…89c3
0x34b655…2a6f
4 touches
1 conflict
0x2a9e9bd1…5368
0x2a68ba…90c5
4 touches
1 conflict
0x21b32e49…8fa1
0xa6afd3…d132
3 touches
1 conflict
0x1bee5aea…5f61
0x34b655…2a6f
2 touches
0 conflicts
0x232f95c2…1d16
0x34b655…2a6f
2 touches
0 conflicts
0x27099c8c…d9d5
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 0xdd0f9852bc…f2647b
Audit this contract →
← previous block·next block →recent activity