← previous blocknext block →recent activity
Analyzing
Block #100,854,901
11 transactions · 11 stateful · 2026-08-31 20:46:21 UTC
Parallelism
64/100
Blocked
27%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,854,901 · 11 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
3w04w15w26w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc06f342…aa8b
0x40c49f…2af0
8 touches
6 conflicts
0x002fed35…79fa
0x2a68ba…90c5
8 touches
6 conflicts
0x2b54cadb…4425
0xd18b7e…414b
8 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
8 touches
6 conflicts
0x4c1fbdf6…953d
0x754704…b603
2 touches
0 conflicts
0x595233b5…c4aa
0x754704…b603
2 touches
0 conflicts
0x91eb94de…b47b
0x754704…b603
2 touches
0 conflicts
0x01a89030…f786
0x98dc6e…8633
2 touches
0 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: 0x40c49f17…d22af0
6 conflicts on slot 0xcc06f34230…43aa8b
Audit this contract →
← previous block·next block →recent activity