← previous blocknext block →recent activity
Analyzing
Block #94,486,187
30 transactions · 27 stateful · 2026-08-09 12:13:07 UTC
Parallelism
73/100
Blocked
48%
Avg conflicts / tx
1.37
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #94,486,187 · 30 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w49w510w627w628w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x95c47f03…f1bb
0x34b655…2a6f
16 touches
28 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0xec7d120d…7084
0x34b655…2a6f
8 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x002fed35…79fa
0x2a68ba…90c5
6 touches
3 conflicts
0xe28b1045…52c1
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
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
28 conflicts on slot 0x95c47f0322…51f1bb
Audit this contract →
← previous block·next block →recent activity