← previous blocknext block →recent activity
Analyzing
Block #102,442,091
20 transactions · 19 stateful · 2026-09-06 10:12:10 UTC
Parallelism
70/100
Blocked
42%
Avg conflicts / tx
0.9
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #102,442,091 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w06w17w08w19w210w311w412w519w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
12 touches
15 conflicts
0x626b9be5…9c3a
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x73bb65fc…650d
0x754704…b603
4 touches
1 conflict
0xc98b6062…73eb
0x754704…b603
4 touches
1 conflict
0xd1eae902…bfd4
0x754704…b603
4 touches
1 conflict
0x14b2b355…8ce5
0x99c7a7…8bf0
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
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
15 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity