← previous blocknext block →recent activity
Analyzing
Block #100,601,316
42 transactions · 36 stateful · 2026-08-30 23:30:18 UTC
Parallelism
90/100
Blocked
50%
Avg conflicts / tx
0.69
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,601,316 · 42 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
1w02w04w05w18w09w010w113w214w215w116w217w319w020w121w322w226w329w330w332w133w239w240w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xfbe161dd…757b
0x3bd359…433a
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x71841507…d9a1
0xd32edf…ff58
5 touches
3 conflicts
0x56fab363…5fe9
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity