← previous blocknext block →recent activity
Analyzing
Block #100,587,834
98 transactions · 66 stateful · 2026-08-30 22:22:29 UTC
Parallelism
79/100
Blocked
73%
Avg conflicts / tx
2.46
Longest chain
21 deep
Execution timeline
did this block parallelize well?
view
block #100,587,834 · 98 txs across 21 waves · depth 21
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
wave w14
wave w15
wave w16
wave w17
wave w18
wave w19
wave w20
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w27w09w312w413w516w222w623w724w825w926w1045w347w1178w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
24 touches
66 conflicts
0x889d5e90…929a
0x2a68ba…90c5
22 touches
55 conflicts
0xb26de809…001f
0xd32edf…ff58
21 touches
55 conflicts
0x5778d110…d2e6
0xc8689a…ee79
14 touches
21 conflicts
0xac2a0273…721b
0x34b655…2a6f
12 touches
15 conflicts
0x737acb78…fce8
0x34b655…2a6f
12 touches
15 conflicts
0xdb067026…9eb8
0x2b46c0…1669
10 touches
10 conflicts
0x10abefc9…c9bc
0x2b46c0…1669
10 touches
10 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
66 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity