← previous blocknext block →recent activity
Analyzing
Block #100,602,472
131 transactions · 61 stateful · 2026-08-30 23:36:07 UTC
Parallelism
85/100
Blocked
70%
Avg conflicts / tx
2.06
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #100,602,472 · 131 txs across 19 waves · depth 19
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w028w230w331w433w535w636w138w742w644w645w746w847w948w1049w1157w12103w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
34 touches
136 conflicts
0x889d5e90…929a
0x2a68ba…90c5
24 touches
66 conflicts
0x00000000…003d
0xa6afd3…d132
16 touches
28 conflicts
0x88ecacda…04c9
0xa6afd3…d132
16 touches
28 conflicts
0x10d80fee…dbda
0x2b46c0…1669
14 touches
21 conflicts
0x40970e69…da50
0x2b46c0…1669
14 touches
21 conflicts
0xad3ef711…4f2b
0x2b46c0…1669
14 touches
21 conflicts
0x5778d110…d2e6
0xc8689a…ee79
14 touches
21 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
136 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity