← previous blocknext block →recent activity
Analyzing
Block #100,621,051
26 transactions · 22 stateful · 2026-08-31 01:09:35 UTC
Parallelism
62/100
Blocked
64%
Avg conflicts / tx
1.96
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #100,621,051 · 26 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w16w27w111w012w113w214w315w416w517w618w719w820w921w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x44ad89ba…cf83
0xe4f6e7…9657
20 touches
45 conflicts
0x724cd9ff…6684
0x0cc9b2…7777
20 touches
45 conflicts
0x00000000…0008
0x0ea966…0742
20 touches
45 conflicts
0x724cd9ff…6684
0xe4f6e7…9657
20 touches
45 conflicts
0xf95c3143…ac6d
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…002f
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x22e0cc1d…ad0d
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: 0xe4f6e757…919657
45 conflicts on slot 0x44ad89ba62…49cf83
Audit this contract →
← previous block·next block →recent activity