← previous blocknext block →recent activity
Analyzing
Block #100,614,182
74 transactions · 61 stateful · 2026-08-31 00:35:02 UTC
Parallelism
78/100
Blocked
79%
Avg conflicts / tx
3.01
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #100,614,182 · 74 txs across 16 waves · depth 16
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w27w08w111w212w313w414w515w616w717w819w121w122w923w447w251w1056w1159w1460w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
22 touches
55 conflicts
0x00000000…0002
0xf5b5f7…6d70
20 touches
45 conflicts
0x889d5e90…929a
0x2a68ba…90c5
20 touches
45 conflicts
0x00000000…003d
0x065c9d…c394
12 touches
15 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
12 touches
15 conflicts
0x00000000…003d
0x851145…3f07
12 touches
15 conflicts
0x31762a87…3704
0x851145…3f07
12 touches
15 conflicts
0xf52df78b…16a0
0x851145…3f07
12 touches
15 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
55 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity