← previous blocknext block →recent activity
Analyzing
Block #102,428,688
23 transactions · 20 stateful · 2026-09-06 09:04:23 UTC
Parallelism
83/100
Blocked
40%
Avg conflicts / tx
0.7
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,428,688 · 23 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
2w05w06w17w28w39w010w115w016w117w219w321w022w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xbbb3076e…3307
0xd32edf…ff58
7 touches
6 conflicts
0xd987be6c…47f1
0x754704…b603
6 touches
3 conflicts
0xf91b744e…9117
0x754704…b603
6 touches
3 conflicts
0x234b8723…d6cd
0x34b655…2a6f
6 touches
3 conflicts
0x6af306bb…2e81
0x3bd359…433a
6 touches
3 conflicts
0x17606ba6…1b6e
0x754704…b603
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
6 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity