← previous blocknext block →recent activity
Analyzing
Block #99,870,286
28 transactions · 25 stateful · 2026-08-28 10:06:48 UTC
Parallelism
75/100
Blocked
40%
Avg conflicts / tx
0.86
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #99,870,286 · 28 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w18w09w111w213w115w216w320w421w524w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x78fe6876…0f5a
0x34b655…2a6f
8 touches
6 conflicts
0x4f2e1481…fa91
0x34b655…2a6f
8 touches
6 conflicts
0xbad4e90b…33a5
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x17a7f697…dcb1
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x0d03bddb…6658
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
6 conflicts on slot 0x78fe687684…5d0f5a
Audit this contract →
← previous block·next block →recent activity