← previous blocknext block →recent activity
Analyzing
Block #100,229,776
17 transactions · 17 stateful · 2026-08-29 16:17:15 UTC
Parallelism
88/100
Blocked
24%
Avg conflicts / tx
0.24
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,229,776 · 17 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
1w06w07w18w09w110w011w116w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc229d8b6…c851
0x928dc8…8207
4 touches
1 conflict
0xaf831072…51d5
0x69a5f9…2fef
4 touches
1 conflict
0xaf831072…51d6
0x69a5f9…2fef
4 touches
1 conflict
0xaf831072…51dc
0x69a5f9…2fef
4 touches
1 conflict
0x2ef1d89b…196d
0x754704…b603
4 touches
1 conflict
0x5311f864…0984
0x754704…b603
4 touches
1 conflict
0xc229d8b6…c84d
0x928dc8…8207
4 touches
1 conflict
0xc229d8b6…c850
0x928dc8…8207
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: 0x928dc8af…fd8207
1 conflict on slot 0xc229d8b6ce…a9c851
Audit this contract →
← previous block·next block →recent activity