← previous blocknext block →recent activity
Analyzing
Block #94,684,303
12 transactions · 11 stateful · 2026-08-10 04:49:34 UTC
Parallelism
83/100
Blocked
9%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #94,684,303 · 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
2w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66dcc428…6df1
0x34b655…2a6f
4 touches
1 conflict
0xcc351d6d…256b
0x34b655…2a6f
4 touches
1 conflict
0xf4f9cac7…fd98
0x34b655…2a6f
4 touches
1 conflict
0x04044393…6c22
0x34b655…2a6f
2 touches
0 conflicts
0x0bfb4aa3…2132
0x34b655…2a6f
2 touches
0 conflicts
0x16cc2b0b…f774
0x34b655…2a6f
2 touches
0 conflicts
0x18de6e82…7ec0
0x34b655…2a6f
2 touches
0 conflicts
0x1bde9f7f…c070
0x34b655…2a6f
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 0x66dcc42858…1f6df1
Audit this contract →
← previous block·next block →recent activity