← previous blocknext block →recent activity
Analyzing
Block #99,202,802
15 transactions · 15 stateful · 2026-08-26 01:53:41 UTC
Parallelism
73/100
Blocked
33%
Avg conflicts / tx
0.73
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,202,802 · 15 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w16w210w311w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe7bd356d…d23b
0x34b655…2a6f
6 touches
3 conflicts
0x130e6564…c565
0x34b655…2a6f
6 touches
3 conflicts
0x41c56387…a8f6
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xe7bd356d…d23a
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
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
3 conflicts on slot 0xe7bd356dd3…abd23b
Audit this contract →
← previous block·next block →recent activity