← previous blocknext block →recent activity
Analyzing
Block #102,419,107
14 transactions · 11 stateful · 2026-09-06 08:15:47 UTC
Parallelism
71/100
Blocked
36%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,419,107 · 14 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w18w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbbc4bdf7…c62f
0x34b655…2a6f
8 touches
6 conflicts
0xd895ee0b…d301
0x34b655…2a6f
6 touches
3 conflicts
0x4859ecba…e51b
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xa0bc4feb…74f2
0x34b655…2a6f
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x4a79535a…24de
0x065c9d…c394
4 touches
1 conflict
0xb87af72a…aef6
0x2a68ba…90c5
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 0xbbc4bdf713…b3c62f
Audit this contract →
← previous block·next block →recent activity