← previous blocknext block →recent activity
Analyzing
Block #94,850,346
16 transactions · 14 stateful · 2026-08-10 18:46:17 UTC
Parallelism
63/100
Blocked
57%
Avg conflicts / tx
1.06
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #94,850,346 · 16 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w27w38w410w412w514w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5767fdec…d9d4
0x34b655…2a6f
10 touches
10 conflicts
0x28ceceef…ecc2
0x34b655…2a6f
8 touches
6 conflicts
0xddd59be0…cddb
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x6e6a8155…9636
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x04994ed2…9032
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
10 conflicts on slot 0x5767fdeca9…38d9d4
Audit this contract →
← previous block·next block →recent activity