← previous blocknext block →recent activity
Analyzing
Block #94,230,269
13 transactions · 13 stateful · 2026-08-08 14:34:24 UTC
Parallelism
62/100
Blocked
38%
Avg conflicts / tx
0.62
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #94,230,269 · 13 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w25w36w07w112w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcef70a96…db44
0x34b655…2a6f
6 touches
3 conflicts
0x3371a69b…441e
0x34b655…2a6f
6 touches
3 conflicts
0x5cacfb02…ef32
0x34b655…2a6f
4 touches
1 conflict
0x734ee320…caae
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6426
0x34b655…2a6f
4 touches
1 conflict
0x09e0690d…6e3d
0xe52b14…7230
4 touches
1 conflict
0x17bbe4f8…08c5
0xe52b14…7230
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 0xcef70a965c…28db44
Audit this contract →
← previous block·next block →recent activity