← previous blocknext block →recent activity
Analyzing
Block #99,359,467
33 transactions · 24 stateful · 2026-08-26 15:02:02 UTC
Parallelism
88/100
Blocked
42%
Avg conflicts / tx
0.48
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,359,467 · 33 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
2w03w07w08w110w011w012w114w115w216w317w122w123w124w228w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5684aadd…8d62
0x34b655…2a6f
6 touches
3 conflicts
0x58757c2a…2513
0x34b655…2a6f
6 touches
3 conflicts
0x443a3e47…f4a4
0x065c9d…c394
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0xd895ee0b…d301
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…004c
0x80c745…7210
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
3 conflicts on slot 0x5684aadd69…f58d62
Audit this contract →
← previous block·next block →recent activity