← previous blocknext block →recent activity
Analyzing
Block #100,625,991
24 transactions · 23 stateful · 2026-08-31 01:34:26 UTC
Parallelism
67/100
Blocked
52%
Avg conflicts / tx
1.17
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #100,625,991 · 24 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w05w110w211w312w413w514w615w116w117w218w222w623w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x61571888…b392
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x9d1d78dc…55b9
0x34b655…2a6f
10 touches
10 conflicts
0x3f81bcfb…2905
0x40c49f…2af0
6 touches
3 conflicts
0x5638f6ef…47bb
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
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: Perpl
15 conflicts on slot 0x6157188898…efb392
Audit this contract →
← previous block·next block →recent activity