← previous blocknext block →recent activity
Analyzing
Block #99,990,243
16 transactions · 15 stateful · 2026-08-28 20:11:16 UTC
Parallelism
69/100
Blocked
47%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,990,243 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w07w18w29w215w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5060cdde…445d
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x9d3ba38e…2371
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0x5086c64a…28ba
0x34b655…2a6f
4 touches
1 conflict
0x628359b1…7263
0x34b655…2a6f
4 touches
1 conflict
0xa1731f0f…1f9d
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 0x5060cdde9e…d4445d
Audit this contract →
← previous block·next block →recent activity