← previous blocknext block →recent activity
Analyzing
Block #100,117,240
10 transactions · 10 stateful · 2026-08-29 06:50:36 UTC
Parallelism
70/100
Blocked
30%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,117,240 · 10 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
4w05w16w07w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x02ab64de…04a8
0x8964d7…10f8
6 touches
3 conflicts
0xef7109b5…7e4f
0x8964d7…10f8
6 touches
3 conflicts
0xef7109b5…7e50
0x8964d7…10f8
6 touches
3 conflicts
0xef7109b5…7e52
0x8964d7…10f8
6 touches
3 conflicts
0x177211e2…1c2d
0x754704…b603
6 touches
3 conflicts
0x2a07e64e…fe77
0x754704…b603
6 touches
3 conflicts
0x02ab64de…04a6
0x8964d7…10f8
6 touches
3 conflicts
0x02ab64de…04a7
0x8964d7…10f8
6 touches
3 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: 0x8964d7c9…5b10f8
3 conflicts on slot 0x02ab64de0a…fd04a8
Audit this contract →
← previous block·next block →recent activity