← previous blocknext block →recent activity
Analyzing
Block #94,948,710
26 transactions · 23 stateful · 2026-08-11 03:01:01 UTC
Parallelism
85/100
Blocked
22%
Avg conflicts / tx
0.42
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #94,948,710 · 26 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w08w09w111w012w015w116w124w225w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4a6b3039…6a98
0x34b655…2a6f
6 touches
3 conflicts
0x734ee320…caae
0x34b655…2a6f
6 touches
3 conflicts
0xfb9f51f4…0f16
0x34b655…2a6f
6 touches
3 conflicts
0x238ee874…7d14
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x2fdfa032…139c
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x64a785e4…0110
0x34b655…2a6f
4 touches
1 conflict
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
3 conflicts on slot 0x4a6b3039f4…046a98
Audit this contract →
← previous block·next block →recent activity