← previous blocknext block →recent activity
Analyzing
Block #94,482,510
21 transactions · 20 stateful · 2026-08-09 11:54:38 UTC
Parallelism
71/100
Blocked
40%
Avg conflicts / tx
0.9
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #94,482,510 · 21 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
2w03w14w25w37w09w011w112w215w319w420w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf4f9cac7…fd98
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x70f537e8…399b
0x34b655…2a6f
4 touches
1 conflict
0x97216283…fd1d
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0xcc351d6d…256b
0x34b655…2a6f
4 touches
1 conflict
0xcd1e3ac5…da86
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
10 conflicts on slot 0xf4f9cac7d9…09fd98
Audit this contract →
← previous block·next block →recent activity