← previous blocknext block →recent activity
Analyzing
Block #100,109,139
16 transactions · 16 stateful · 2026-08-29 06:09:48 UTC
Parallelism
81/100
Blocked
25%
Avg conflicts / tx
0.44
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,109,139 · 16 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
1w03w16w09w010w111w012w215w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0xd23f1622…7f97
0x40c49f…2af0
4 touches
1 conflict
0xe8598784…a22f
0x40c49f…2af0
4 touches
1 conflict
0x02373c43…3cb3
0x34b655…2a6f
4 touches
1 conflict
0x69e7440f…4b7f
0x34b655…2a6f
4 touches
1 conflict
0xedee7e09…6888
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 0xac2a02739b…81721b
Audit this contract →
← previous block·next block →recent activity