← previous blocknext block →recent activity
Analyzing
Block #102,219,678
28 transactions · 27 stateful · 2026-09-05 15:25:19 UTC
Parallelism
86/100
Blocked
33%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,219,678 · 28 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
1w02w14w07w08w110w111w015w116w217w319w221w127w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4262b973…a23f
0x34b655…2a6f
8 touches
6 conflicts
0x641aed07…bcb9
0x34b655…2a6f
8 touches
6 conflicts
0xd66696e0…0842
0x34b655…2a6f
8 touches
6 conflicts
0xac8f427e…e307
0x34b655…2a6f
7 touches
6 conflicts
0xc824469a…641f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x9cf9008a…d826
0x34b655…2a6f
5 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
6 conflicts on slot 0x4262b9731b…52a23f
Audit this contract →
← previous block·next block →recent activity