← previous blocknext block →recent activity
Analyzing
Block #100,235,683
17 transactions · 16 stateful · 2026-08-29 16:46:59 UTC
Parallelism
88/100
Blocked
13%
Avg conflicts / tx
0.12
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,235,683 · 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
2w03w110w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaf831072…51dc
0x69a5f9…2fef
4 touches
1 conflict
0x2ef1d89b…196d
0x754704…b603
4 touches
1 conflict
0x00000000…0036
0x35a73b…6042
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0xaf831072…51d5
0x69a5f9…2fef
4 touches
1 conflict
0xaf831072…51d6
0x69a5f9…2fef
4 touches
1 conflict
0xb543d97e…cc3f
0x34b655…2a6f
2 touches
0 conflicts
0xbde524f4…43bf
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: 0x69a5f9ad…102fef
1 conflict on slot 0xaf831072f6…c551dc
Audit this contract →
← previous block·next block →recent activity