← previous blocknext block →recent activity
Analyzing
Block #94,751,126
17 transactions · 17 stateful · 2026-08-10 10:26:53 UTC
Parallelism
88/100
Blocked
6%
Avg conflicts / tx
0.12
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #94,751,126 · 17 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
3w06w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x13880d72…08c2
0x065c9d…c394
2 touches
0 conflicts
0x160f117d…8e90
0x065c9d…c394
2 touches
0 conflicts
0x4a65f77f…1f54
0x065c9d…c394
2 touches
0 conflicts
0x8c24533d…9cfc
0x065c9d…c394
2 touches
0 conflicts
0x8d0ad6bc…5fe0
0x065c9d…c394
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 0x0000000000…0000c9
Audit this contract →
← previous block·next block →recent activity