← previous blocknext block →recent activity
Analyzing
Block #99,884,583
18 transactions · 17 stateful · 2026-08-28 11:18:49 UTC
Parallelism
67/100
Blocked
29%
Avg conflicts / tx
0.83
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,884,583 · 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
6w07w110w211w312w414w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x247cfb80…cca8
0x34b655…2a6f
12 touches
15 conflicts
0x1b62550e…f9a8
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x6183ee9a…21b1
0x34b655…2a6f
4 touches
1 conflict
0xc17ee2bb…ff08
0x34b655…2a6f
4 touches
1 conflict
0x81f65578…8168
0x34b655…2a6f
4 touches
1 conflict
0xc51a62ac…f472
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
15 conflicts on slot 0x247cfb80ae…c4cca8
Audit this contract →
← previous block·next block →recent activity