← previous blocknext block →recent activity
Analyzing
Block #99,852,358
20 transactions · 18 stateful · 2026-08-28 08:36:19 UTC
Parallelism
65/100
Blocked
50%
Avg conflicts / tx
1.3
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #99,852,358 · 20 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
1w02w14w26w08w110w211w314w415w316w517w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x24e21006…a377
0x34b655…2a6f
12 touches
15 conflicts
0x22f10271…841d
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xdbc6e634…e16c
0x1b6862…e19c
4 touches
1 conflict
0x00000000…00c9
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 0x24e2100637…d0a377
Audit this contract →
← previous block·next block →recent activity