← previous blocknext block →recent activity
Analyzing
Block #100,699,169
15 transactions · 10 stateful · 2026-08-31 07:42:32 UTC
Parallelism
80/100
Blocked
30%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,699,169 · 15 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
2w03w14w05w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7f7fb616…f7d8
0x34b655…2a6f
6 touches
3 conflicts
0x81ca8c9e…28cb
0x34b655…2a6f
4 touches
1 conflict
0xa6b48d6e…0705
0x34b655…2a6f
4 touches
1 conflict
0x5a39b0ae…eae3
0x34b655…2a6f
4 touches
1 conflict
0x451e482b…7e7d
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0x575a11d2…e67a
0x34b655…2a6f
2 touches
0 conflicts
0x59991669…58c6
0x34b655…2a6f
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
3 conflicts on slot 0x7f7fb616c7…12f7d8
Audit this contract →
← previous block·next block →recent activity