← previous blocknext block →recent activity
Analyzing
Block #94,972,253
12 transactions · 12 stateful · 2026-08-11 04:59:25 UTC
Parallelism
83/100
Blocked
17%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #94,972,253 · 12 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe1a1a29a…a398
0x34b655…2a6f
4 touches
1 conflict
0xe1a1a29a…a399
0x34b655…2a6f
4 touches
1 conflict
0x8cba8eb6…d605
0x34b655…2a6f
4 touches
1 conflict
0xcda18b0b…6a4c
0x34b655…2a6f
4 touches
1 conflict
0x3286d0f0…b306
0x34b655…2a6f
3 touches
1 conflict
0x96abf0d5…cb0b
0xd32edf…ff58
3 touches
1 conflict
0x00000000…001e
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…002e
0x1b6862…e19c
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
1 conflict on slot 0xe1a1a29a1a…3aa398
Audit this contract →
← previous block·next block →recent activity