← previous blocknext block →recent activity
Analyzing
Block #100,786,388
42 transactions · 35 stateful · 2026-08-31 15:01:26 UTC
Parallelism
88/100
Blocked
49%
Avg conflicts / tx
0.6
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,786,388 · 42 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w25w06w08w09w110w111w113w114w215w120w221w225w327w028w430w132w336w037w138w239w041w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd6412ec3…a35c
0x34b655…2a6f
6 touches
3 conflicts
0xf984d8ab…6e4f
0x34b655…2a6f
6 touches
3 conflicts
0x76622fb2…4f08
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x00000000…002a
0x1b6862…e19c
4 touches
1 conflict
0x26bb6db7…f85e
0x1b6862…e19c
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 0xd6412ec321…9aa35c
Audit this contract →
← previous block·next block →recent activity