← previous blocknext block →recent activity
Analyzing
Block #100,728,444
23 transactions · 23 stateful · 2026-08-31 10:09:48 UTC
Parallelism
65/100
Blocked
61%
Avg conflicts / tx
1.43
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #100,728,444 · 23 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w06w17w08w19w210w111w212w313w414w516w117w219w620w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…0002
0xf5b5f7…6d70
6 touches
3 conflicts
0x9eaed5a0…9f17
0x34b655…2a6f
6 touches
3 conflicts
0xb3c577ab…b3a1
0x34b655…2a6f
6 touches
3 conflicts
0x25180879…8191
0x34b655…2a6f
4 touches
1 conflict
0x382434ca…96b5
0x34b655…2a6f
4 touches
1 conflict
0x451e482b…7e7d
0x34b655…2a6f
4 touches
1 conflict
0x4a45b318…9716
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
15 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity