← previous blocknext block →recent activity
Analyzing
Block #100,919,793
21 transactions · 20 stateful · 2026-09-01 02:12:45 UTC
Parallelism
67/100
Blocked
55%
Avg conflicts / tx
1.33
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,919,793 · 21 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w15w26w37w010w111w212w313w415w416w517w620w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe4978fe2…7b9b
0x34b655…2a6f
10 touches
10 conflicts
0xa1087a5c…66c4
0x754704…b603
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x2827ae77…4368
0x34b655…2a6f
6 touches
3 conflicts
0x0778475b…bd75
0x2a68ba…90c5
6 touches
3 conflicts
0x4d51942e…d78b
0x065c9d…c394
5 touches
3 conflicts
0x3cb7ee74…b8a5
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
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
10 conflicts on slot 0xe4978fe2a3…037b9b
Audit this contract →
← previous block·next block →recent activity