← previous blocknext block →recent activity
Analyzing
Block #100,566,276
21 transactions · 18 stateful · 2026-08-30 20:34:02 UTC
Parallelism
86/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,566,276 · 21 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
13w014w117w120w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xae7f6f8f…b68a
0x34b655…2a6f
4 touches
1 conflict
0x2202504e…fad0
0x34b655…2a6f
4 touches
1 conflict
0x4c29ecd5…58b6
0x34b655…2a6f
4 touches
1 conflict
0x5186b669…b761
0x34b655…2a6f
4 touches
1 conflict
0x5efd7300…d8a5
0x34b655…2a6f
4 touches
1 conflict
0x7e06d07b…36af
0x34b655…2a6f
4 touches
1 conflict
0x7e06d07b…36b0
0x34b655…2a6f
4 touches
1 conflict
0x809f2ba8…89d3
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
1 conflict on slot 0xae7f6f8f38…c9b68a
Audit this contract →
← previous block·next block →recent activity