← previous blocknext block →recent activity
Analyzing
Block #100,600,959
36 transactions · 29 stateful · 2026-08-30 23:28:30 UTC
Parallelism
83/100
Blocked
45%
Avg conflicts / tx
0.53
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,600,959 · 36 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w07w09w113w014w116w117w222w023w124w328w129w130w231w132w234w435w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x065ff70b…356d
0x40c49f…2af0
6 touches
3 conflicts
0x1e168c8b…6945
0x34b655…2a6f
6 touches
3 conflicts
0x0d622e34…0000
0x681e90…ae09
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x7c08286a…ecaa
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
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: 0x40c49f17…d22af0
3 conflicts on slot 0x065ff70bfe…b9356d
Audit this contract →
← previous block·next block →recent activity