← previous blocknext block →recent activity
Analyzing
Block #100,979,113
22 transactions · 20 stateful · 2026-09-01 07:11:08 UTC
Parallelism
82/100
Blocked
40%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,979,113 · 22 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w05w16w07w19w212w316w119w020w121w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd814f518…f5b4
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x1a2e73cf…5ff5
0x34b655…2a6f
4 touches
1 conflict
0x1b3c88ab…46ce
0x34b655…2a6f
4 touches
1 conflict
0x2f1306dc…5e0c
0x34b655…2a6f
4 touches
1 conflict
0x3fd179f5…8247
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
3 conflicts on slot 0xd814f51828…c6f5b4
Audit this contract →
← previous block·next block →recent activity