← previous blocknext block →recent activity
Analyzing
Block #100,143,089
15 transactions · 15 stateful · 2026-08-29 09:00:53 UTC
Parallelism
80/100
Blocked
33%
Avg conflicts / tx
0.53
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,143,089 · 15 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w05w17w09w010w111w112w214w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x16269ba2…a1ea
0x8964d7…10f8
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x2a07e64e…fe77
0x754704…b603
6 touches
3 conflicts
0x00000000…0008
0x8964d7…10f8
6 touches
3 conflicts
0x16269ba2…a1e3
0x8964d7…10f8
6 touches
3 conflicts
0x16269ba2…a1e4
0x8964d7…10f8
6 touches
3 conflicts
0x16269ba2…a1e7
0x8964d7…10f8
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: 0x8964d7c9…5b10f8
3 conflicts on slot 0x16269ba2ce…52a1ea
Audit this contract →
← previous block·next block →recent activity