← previous blocknext block →recent activity
Analyzing
Block #100,600,822
55 transactions · 44 stateful · 2026-08-30 23:27:49 UTC
Parallelism
64/100
Blocked
70%
Avg conflicts / tx
2.98
Longest chain
20 deep
Execution timeline
did this block parallelize well?
view
block #100,600,822 · 55 txs across 20 waves · depth 20
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w27w38w425w528w630w747w1350w1654w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
24 touches
66 conflicts
0x482471ad…122f
0x34b655…2a6f
22 touches
55 conflicts
0xc824469a…6425
0x34b655…2a6f
22 touches
55 conflicts
0xffb9d957…d397
0xd32edf…ff58
17 touches
36 conflicts
0xb409e204…89ac
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…0002
0xf5b5f7…6d70
8 touches
6 conflicts
0x7c61fbae…d54c
0x34b655…2a6f
8 touches
6 conflicts
0xfd7f5b55…4994
0x34b655…2a6f
8 touches
6 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