← previous blocknext block →recent activity
Analyzing
Block #94,484,112
18 transactions · 17 stateful · 2026-08-09 12:02:41 UTC
Parallelism
67/100
Blocked
41%
Avg conflicts / tx
1.17
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #94,484,112 · 18 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
2w03w04w15w26w37w211w014w116w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc351d6d…256b
0x34b655…2a6f
10 touches
10 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0x737acb78…fce8
0x34b655…2a6f
8 touches
6 conflicts
0xf4f9cac7…fd98
0x34b655…2a6f
6 touches
3 conflicts
0x5890394d…3000
0x34b655…2a6f
6 touches
3 conflicts
0xec7d120d…7084
0x34b655…2a6f
6 touches
3 conflicts
0x845ec8b0…c1af
0x34b655…2a6f
4 touches
1 conflict
0x8c6488e4…a6e0
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 0xcc351d6dd2…b1256b
Audit this contract →
← previous block·next block →recent activity