← previous blocknext block →recent activity
Analyzing
Block #94,201,080
13 transactions · 11 stateful · 2026-08-08 12:06:31 UTC
Parallelism
69/100
Blocked
27%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #94,201,080 · 13 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
1w06w17w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0a2300ab…81c7
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xe4af4c87…9964
0x34b655…2a6f
4 touches
1 conflict
0x07218f94…f9ac
0x34b655…2a6f
2 touches
0 conflicts
0x1e56edff…5f5b
0x34b655…2a6f
2 touches
0 conflicts
0x46822f8c…d048
0x34b655…2a6f
2 touches
0 conflicts
0x54f4214e…d0eb
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
3 conflicts on slot 0x0a2300abf9…9281c7
Audit this contract →
← previous block·next block →recent activity