← previous blocknext block →recent activity
Analyzing
Block #100,600,266
56 transactions · 30 stateful · 2026-08-30 23:25:01 UTC
Parallelism
82/100
Blocked
63%
Avg conflicts / tx
0.96
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #100,600,266 · 56 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
4w06w17w29w310w412w513w615w016w018w130w242w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0x889d5e90…929a
0x2a68ba…90c5
14 touches
21 conflicts
0x10abefc9…c9bc
0x2b46c0…1669
10 touches
10 conflicts
0x10d80fee…dbda
0x2b46c0…1669
10 touches
10 conflicts
0x5778d110…d2e6
0xc8689a…ee79
10 touches
10 conflicts
0xd6bd849a…5597
0x2a68ba…90c5
10 touches
10 conflicts
0x1d10f24a…2fb8
0xa6afd3…d132
10 touches
10 conflicts
0x8cf3d245…1d0d
0x2b46c0…1669
10 touches
10 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: Perpl
21 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity