← previous blocknext block →recent activity
Analyzing
Block #100,600,398
24 transactions · 20 stateful · 2026-08-30 23:25:41 UTC
Parallelism
63/100
Blocked
55%
Avg conflicts / tx
0.83
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #100,600,398 · 24 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w17w211w313w114w415w516w620w121w222w723w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x24e6ab11…e317
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x155e52ca…fac7
0x34b655…2a6f
6 touches
3 conflicts
0xd5b10148…e637
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x109d8a52…a7b7
0x34b655…2a6f
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
6 conflicts on slot 0x24e6ab11f2…a0e317
Audit this contract →
← previous block·next block →recent activity