← previous blocknext block →recent activity
Analyzing
Block #100,082,875
31 transactions · 27 stateful · 2026-08-29 03:57:34 UTC
Parallelism
68/100
Blocked
56%
Avg conflicts / tx
1.9
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #100,082,875 · 31 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
2w03w04w08w19w210w314w415w519w120w422w123w624w726w827w228w330w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
18 touches
36 conflicts
0x482471ad…122f
0x34b655…2a6f
16 touches
28 conflicts
0xfd5482c3…7e73
0x34b655…2a6f
14 touches
21 conflicts
0x627738d1…db02
0x34b655…2a6f
14 touches
21 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x206f4379…e08a
0x34b655…2a6f
6 touches
3 conflicts
0x08e8f2c9…a11a
0x34b655…2a6f
6 touches
3 conflicts
0xfc81faf7…1417
0x34b655…2a6f
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
36 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity