← previous blocknext block →recent activity
Analyzing
Block #100,748,566
17 transactions · 17 stateful · 2026-08-31 11:51:01 UTC
Parallelism
65/100
Blocked
53%
Avg conflicts / tx
1.12
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,748,566 · 17 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w26w07w18w29w310w414w315w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x11b69a7e…334e
0x01bff4…1071
10 touches
10 conflicts
0x002fed35…79fa
0x2a68ba…90c5
10 touches
10 conflicts
0x00f8e79a…3871
0x851145…3f07
10 touches
10 conflicts
0xa1087a5c…66c4
0x754704…b603
10 touches
10 conflicts
0xbc8fb280…76a3
0x34b655…2a6f
8 touches
6 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
8 touches
6 conflicts
0x2b093939…9084
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
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: 0x01bff417…bc1071
10 conflicts on slot 0x11b69a7ea1…83334e
Audit this contract →
← previous block·next block →recent activity