← previous blocknext block →recent activity
Analyzing
Block #94,134,449
22 transactions · 21 stateful · 2026-08-08 06:28:52 UTC
Parallelism
73/100
Blocked
38%
Avg conflicts / tx
0.68
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #94,134,449 · 22 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
1w03w04w16w27w18w39w410w011w113w114w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4e87a718…1764
0x34b655…2a6f
8 touches
6 conflicts
0xfb31d278…9107
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x3bdd71a2…b6eb
0x34b655…2a6f
4 touches
1 conflict
0x4e9f9722…8054
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc2b37cdc…e470
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
6 conflicts on slot 0x4e87a718cd…7b1764
Audit this contract →
← previous block·next block →recent activity