← previous blocknext block →recent activity
Analyzing
Block #100,232,391
15 transactions · 14 stateful · 2026-08-29 16:30:25 UTC
Parallelism
87/100
Blocked
29%
Avg conflicts / tx
0.27
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,232,391 · 15 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w06w07w110w111w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x52c281e4…66f6
0x40c49f…2af0
4 touches
1 conflict
0xaeb5864c…7679
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x532b7e06…cdfc
0x34b655…2a6f
4 touches
1 conflict
0xb0b0260c…51c4
0x34b655…2a6f
4 touches
1 conflict
0xb839a1e8…22b3
0x34b655…2a6f
4 touches
1 conflict
0xbec23443…9293
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641f
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: 0x40c49f17…d22af0
1 conflict on slot 0x52c281e467…f666f6
Audit this contract →
← previous block·next block →recent activity