← previous blocknext block →recent activity
Analyzing
Block #99,870,583
23 transactions · 21 stateful · 2026-08-28 10:08:17 UTC
Parallelism
61/100
Blocked
62%
Avg conflicts / tx
1.57
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #99,870,583 · 23 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w27w38w29w311w412w514w615w417w621w722w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x68dfc6ca…56ac
0x34b655…2a6f
12 touches
15 conflicts
0xe3ac42d3…831b
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0018
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0028
0x1b6862…e19c
6 touches
3 conflicts
0xba5743c7…21bf
0x1b6862…e19c
6 touches
3 conflicts
0xab60dc09…85e4
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
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 0x68dfc6ca63…a056ac
Audit this contract →
← previous block·next block →recent activity