← previous blocknext block →recent activity
Analyzing
Block #100,145,951
11 transactions · 10 stateful · 2026-08-29 09:15:17 UTC
Parallelism
73/100
Blocked
20%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,145,951 · 11 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
7w08w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8620ddb9…5114
0x8964d7…10f8
6 touches
3 conflicts
0x2a07e64e…fe77
0x754704…b603
6 touches
3 conflicts
0x00000000…0008
0x8964d7…10f8
6 touches
3 conflicts
0x8620ddb9…510d
0x8964d7…10f8
6 touches
3 conflicts
0x8620ddb9…510e
0x8964d7…10f8
6 touches
3 conflicts
0x8620ddb9…5111
0x8964d7…10f8
6 touches
3 conflicts
0x8620ddb9…5112
0x8964d7…10f8
6 touches
3 conflicts
0x0e1d1106…f5b9
0x8964d7…10f8
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: 0x8964d7c9…5b10f8
3 conflicts on slot 0x8620ddb9e5…095114
Audit this contract →
← previous block·next block →recent activity