← previous blocknext block →recent activity
Analyzing
Block #100,109,043
19 transactions · 18 stateful · 2026-08-29 06:09:19 UTC
Parallelism
79/100
Blocked
33%
Avg conflicts / tx
0.53
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,109,043 · 19 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
1w04w05w17w29w010w111w212w315w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…00c9
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…641f
0x34b655…2a6f
8 touches
6 conflicts
0x42e5184f…4e8b
0x34b655…2a6f
8 touches
6 conflicts
0x38bcfe5f…6c71
0x34b655…2a6f
8 touches
6 conflicts
0x0803214f…d4d5
0x34b655…2a6f
8 touches
6 conflicts
0xbceecf11…0120
0x34b655…2a6f
7 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xfcb7b8b2…ebb3
0x065c9d…c394
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 0x0000000000…0000c9
Audit this contract →
← previous block·next block →recent activity