← previous blocknext block →recent activity
Analyzing
Block #94,481,198
70 transactions · 70 stateful · 2026-08-09 11:48:02 UTC
Parallelism
94/100
Blocked
4%
Avg conflicts / tx
0.09
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #94,481,198 · 70 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
1w03w14w267w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66bdb4c2…7ea6
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xfc421e5f…71c0
0x34b655…2a6f
4 touches
1 conflict
0x147c952c…b00d
0x34b655…2a6f
4 touches
1 conflict
0xebc963ef…7eae
0x34b655…2a6f
4 touches
1 conflict
0x949fc5d9…55f3
0x34b655…2a6f
4 touches
1 conflict
0x78ea1843…50f7
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x447d2e…e9f5
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
6 conflicts on slot 0x66bdb4c268…a97ea6
Audit this contract →
← previous block·next block →recent activity