← previous blocknext block →recent activity
Analyzing
Block #100,607,241
50 transactions · 45 stateful · 2026-08-31 00:00:07 UTC
Parallelism
80/100
Blocked
69%
Avg conflicts / tx
1.88
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #100,607,241 · 50 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w05w16w17w18w09w110w012w113w214w321w222w323w424w529w135w236w138w339w240w441w242w546w647w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xf5b5f7…6d70
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x61571888…b392
0x34b655…2a6f
12 touches
15 conflicts
0xca841faa…486a
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x5f77d607…2c84
0x065c9d…c394
8 touches
6 conflicts
0x6cc500b1…55cd
0x34b655…2a6f
8 touches
6 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: 0xf5b5f7f8…a36d70
28 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity