← previous blocknext block →recent activity
Analyzing
Block #100,608,834
40 transactions · 34 stateful · 2026-08-31 00:08:08 UTC
Parallelism
70/100
Blocked
68%
Avg conflicts / tx
1.63
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #100,608,834 · 40 txs across 12 waves · depth 12
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w25w38w09w110w411w012w113w214w317w121w323w424w226w527w528w633w535w736w838w1039w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0x065ff70b…356d
0x40c49f…2af0
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x40c49f…2af0
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: Perpl
28 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity