← previous blocknext block →recent activity
Analyzing
Block #100,127,399
12 transactions · 12 stateful · 2026-08-29 07:41:45 UTC
Parallelism
75/100
Blocked
25%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,127,399 · 12 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
7w08w19w210w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9d6c2e85…664c
0x8964d7…10f8
6 touches
3 conflicts
0x9d6c2e85…664d
0x8964d7…10f8
6 touches
3 conflicts
0x9d6c2e85…6650
0x8964d7…10f8
6 touches
3 conflicts
0x9d6c2e85…6651
0x8964d7…10f8
6 touches
3 conflicts
0x9d6c2e85…6652
0x8964d7…10f8
6 touches
3 conflicts
0x7c06078c…05b6
0x8964d7…10f8
6 touches
3 conflicts
0x7c06078c…05b7
0x8964d7…10f8
6 touches
3 conflicts
0x7c06078c…05b9
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 0x9d6c2e8532…3c664c
Audit this contract →
← previous block·next block →recent activity