← previous blocknext block →recent activity
Analyzing
Block #100,920,230
29 transactions · 28 stateful · 2026-09-01 02:14:57 UTC
Parallelism
79/100
Blocked
46%
Avg conflicts / tx
0.93
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,920,230 · 29 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w15w07w09w110w212w213w314w315w417w018w119w020w122w125w226w027w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x6caf33e2…c261
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x0778475b…bd75
0x2a68ba…90c5
6 touches
3 conflicts
0xc16b9fa2…e57e
0x34b655…2a6f
6 touches
3 conflicts
0x297706f8…af34
0x065c9d…c394
5 touches
3 conflicts
0x97420b44…a2a8
0x34b655…2a6f
4 touches
1 conflict
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
6 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity