← previous blocknext block →recent activity
Analyzing
Block #108,619,636
33 transactions · 29 stateful · 2026-09-28 01:25:45 UTC
Parallelism
79/100
Blocked
59%
Avg conflicts / tx
1.3
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #108,619,636 · 33 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
1w02w14w05w06w17w28w09w110w011w112w113w215w320w121w222w323w424w525w327w332w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x471711ec…240a
0x34b655…2a6f
10 touches
10 conflicts
0x3af28597…dcef
0x34b655…2a6f
8 touches
6 conflicts
0xf3d7a307…4d63
0x065c9d…c394
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x268c1467…5702
0x065c9d…c394
6 touches
3 conflicts
0xba38536d…2b7d
0x065c9d…c394
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
21 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity