← previous blocknext block →recent activity
Analyzing
Block #94,468,365
6 transactions · 6 stateful · 2026-08-09 10:43:26 UTC
Parallelism
67/100
Blocked
33%
Avg conflicts / tx
0.33
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #94,468,365 · 6 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
1w02w03w14w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf7019ae9…bfb0
0x34b655…2a6f
4 touches
1 conflict
0x002fed35…79fa
0x2a68ba…90c5
4 touches
1 conflict
0xe1d743ba…11c9
0x34b655…2a6f
4 touches
1 conflict
0x6da4f117…7f9c
0x065c9d…c394
3 touches
1 conflict
0x2846597d…7217
0x34b655…2a6f
2 touches
0 conflicts
0x320701d5…f9f3
0x34b655…2a6f
2 touches
0 conflicts
0x320701d5…f9f4
0x34b655…2a6f
2 touches
0 conflicts
0x32d8a305…96ee
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 0xf7019ae914…4cbfb0
Audit this contract →
← previous block·next block →recent activity