← previous blocknext block →recent activity
Analyzing
Block #94,681,355
12 transactions · 11 stateful · 2026-08-10 04:34:45 UTC
Parallelism
83/100
Blocked
18%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #94,681,355 · 12 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
1w02w13w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd66696e0…0842
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0d88d35b…ed58
0x065c9d…c394
2 touches
0 conflicts
0x144b3c9e…dfc5
0x065c9d…c394
2 touches
0 conflicts
0x21898044…a071
0x065c9d…c394
2 touches
0 conflicts
0x81eda938…ae32
0x065c9d…c394
2 touches
0 conflicts
0xcfa9628f…1658
0x065c9d…c394
2 touches
0 conflicts
0xf3e56233…2744
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 0xd66696e0dc…230842
Audit this contract →
← previous block·next block →recent activity