← previous blocknext block →recent activity
Analyzing
Block #94,697,329
14 transactions · 12 stateful · 2026-08-10 05:55:05 UTC
Parallelism
57/100
Blocked
67%
Avg conflicts / tx
1.07
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #94,697,329 · 14 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
1w02w03w14w16w27w38w410w311w412w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd66696e0…0842
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xa03c2a35…52e6
0x34b655…2a6f
8 touches
6 conflicts
0x08d1d6b7…4bb3
0x34b655…2a6f
8 touches
6 conflicts
0xe8d58d34…426d
0x34b655…2a6f
6 touches
3 conflicts
0x331eb8c3…e3de
0x34b655…2a6f
6 touches
3 conflicts
0xbb322930…ace5
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0xd66696e0dc…230842
Audit this contract →
← previous block·next block →recent activity