← previous blocknext block →recent activity
Analyzing
Block #100,738,504
35 transactions · 33 stateful · 2026-08-31 11:00:24 UTC
Parallelism
71/100
Blocked
61%
Avg conflicts / tx
1.77
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #100,738,504 · 35 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w05w08w19w211w312w413w516w625w226w730w533w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbf303bde…ce5a
0x34b655…2a6f
14 touches
21 conflicts
0xa1087a5c…66c4
0x754704…b603
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x11b69a7e…334e
0x01bff4…1071
10 touches
10 conflicts
0x70986451…c6bd
0x34b655…2a6f
8 touches
6 conflicts
0x002fed35…79fa
0x2a68ba…90c5
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 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
21 conflicts on slot 0xbf303bde1e…cace5a
Audit this contract →
← previous block·next block →recent activity