← previous blocknext block →recent activity
Analyzing
Block #99,858,252
23 transactions · 23 stateful · 2026-08-28 09:06:09 UTC
Parallelism
83/100
Blocked
48%
Avg conflicts / tx
0.91
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,858,252 · 23 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w06w17w210w011w112w113w216w017w118w219w321w022w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc16e646d…4fb0
0x34b655…2a6f
8 touches
6 conflicts
0xd17580f9…ece1
0x754704…b603
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xbd22d0fc…64fd
0x34b655…2a6f
6 touches
3 conflicts
0x33893bb4…5522
0xd32edf…ff58
5 touches
3 conflicts
0xba5743c7…21bf
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
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 0xc16e646d81…a44fb0
Audit this contract →
← previous block·next block →recent activity