← previous blocknext block →recent activity
Analyzing
Block #100,852,017
30 transactions · 26 stateful · 2026-08-31 20:31:50 UTC
Parallelism
70/100
Blocked
42%
Avg conflicts / tx
0.7
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #100,852,017 · 30 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w28w211w312w414w015w016w120w522w326w627w728w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x21280422…0930
0x34b655…2a6f
8 touches
6 conflicts
0x140223cf…9ccc
0x34b655…2a6f
8 touches
6 conflicts
0x5c455afd…ce06
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…002b
0x1b6862…e19c
4 touches
1 conflict
0xac79a0c7…be12
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x4e58deff…c5d0
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: Perpl
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity