← previous blocknext block →recent activity
Analyzing
Block #102,482,208
18 transactions · 17 stateful · 2026-09-06 13:35:31 UTC
Parallelism
72/100
Blocked
47%
Avg conflicts / tx
1.11
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #102,482,208 · 18 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w17w08w19w210w311w413w214w316w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0a6a3b04…669b
0x34b655…2a6f
10 touches
10 conflicts
0xd17580f9…ece1
0x754704…b603
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x9ca6fa7b…aeb3
0x34b655…2a6f
6 touches
3 conflicts
0x22f10271…841d
0x34b655…2a6f
6 touches
3 conflicts
0x83f3d320…fb59
0x34b655…2a6f
4 touches
1 conflict
0x109d8a52…a7b7
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
10 conflicts on slot 0x0a6a3b04e3…a7669b
Audit this contract →
← previous block·next block →recent activity