← previous blocknext block →recent activity
Analyzing
Block #94,716,694
11 transactions · 9 stateful · 2026-08-10 07:32:29 UTC
Parallelism
82/100
Blocked
11%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #94,716,694 · 11 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
1w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1c6b666d…4943
0x34b655…2a6f
4 touches
1 conflict
0xc7b1189e…d092
0x34b655…2a6f
4 touches
1 conflict
0x0a2131b3…455e
0x34b655…2a6f
2 touches
0 conflicts
0x0a799c4d…2b92
0x34b655…2a6f
2 touches
0 conflicts
0x0e1dab48…e4b7
0x34b655…2a6f
2 touches
0 conflicts
0x1f8ecef7…5af3
0x34b655…2a6f
2 touches
0 conflicts
0x29eb4d5c…a77c
0x34b655…2a6f
2 touches
0 conflicts
0x3405ed3a…6ee6
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 0x1c6b666df4…894943
Audit this contract →
← previous block·next block →recent activity