← previous blocknext block →recent activity
Analyzing
Block #100,438,802
22 transactions · 22 stateful · 2026-08-30 09:52:40 UTC
Parallelism
86/100
Blocked
18%
Avg conflicts / tx
0.18
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,438,802 · 22 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
1w02w03w15w112w013w119w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x364d1d02…0528
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xbe6835a1…a184
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x651d4cdd…66a7
0x34b655…2a6f
4 touches
1 conflict
0x651d4cdd…66a6
0x34b655…2a6f
4 touches
1 conflict
0x4cff6b80…47a8
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 0x364d1d0233…140528
Audit this contract →
← previous block·next block →recent activity