← previous blocknext block →recent activity
Analyzing
Block #100,924,296
24 transactions · 22 stateful · 2026-09-01 02:35:24 UTC
Parallelism
71/100
Blocked
59%
Avg conflicts / tx
1.46
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,924,296 · 24 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
1w02w13w06w08w110w211w312w413w214w515w216w319w621w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x382434ca…96b5
0x34b655…2a6f
12 touches
15 conflicts
0x19db4c1d…a025
0x34b655…2a6f
10 touches
10 conflicts
0xa1087a5c…66c4
0x754704…b603
10 touches
10 conflicts
0x36347244…0823
0x065c9d…c394
8 touches
6 conflicts
0x002fed35…79fa
0x2a68ba…90c5
8 touches
6 conflicts
0x85bfd0af…ce96
0x34b655…2a6f
8 touches
6 conflicts
0x421e897b…37da
0x34b655…2a6f
6 touches
3 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
6 touches
3 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
15 conflicts on slot 0x382434ca57…4d96b5
Audit this contract →
← previous block·next block →recent activity