← previous blocknext block →recent activity
Analyzing
Block #100,699,134
13 transactions · 11 stateful · 2026-08-31 07:42:21 UTC
Parallelism
85/100
Blocked
9%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,699,134 · 13 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
5w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa6b48d6e…0705
0x34b655…2a6f
4 touches
1 conflict
0x27efabcb…567c
0x34b655…2a6f
4 touches
1 conflict
0x2827ae77…4368
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0x524f0872…0d12
0x34b655…2a6f
4 touches
1 conflict
0x5a39b0ae…eae3
0x34b655…2a6f
4 touches
1 conflict
0x7f7fb616…f7d8
0x34b655…2a6f
4 touches
1 conflict
0x15c6ded9…48e7
0x754704…b603
2 touches
0 conflicts
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
1 conflict on slot 0xa6b48d6e52…7c0705
Audit this contract →
← previous block·next block →recent activity