← previous blocknext block →recent activity
Analyzing
Block #100,143,976
50 transactions · 43 stateful · 2026-08-29 09:05:21 UTC
Parallelism
72/100
Blocked
74%
Avg conflicts / tx
2.1
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #100,143,976 · 50 txs across 14 waves · depth 14
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
wave w12
wave w13
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w28w210w011w312w415w016w117w018w119w220w321w422w523w624w725w827w131w240w342w1044w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x61571888…b392
0x34b655…2a6f
18 touches
36 conflicts
0x00000000…0002
0xf5b5f7…6d70
18 touches
36 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x68e9cd57…b5be
0x34b655…2a6f
12 touches
15 conflicts
0xfcb7b8b2…ebb3
0x065c9d…c394
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x0d622e34…0000
0x681e90…ae09
6 touches
3 conflicts
0x11258774…9892
0x2a68ba…90c5
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 0x6157188898…efb392
Audit this contract →
← previous block·next block →recent activity