← previous blocknext block →recent activity
Analyzing
Block #102,327,114
19 transactions · 14 stateful · 2026-09-06 00:29:45 UTC
Parallelism
79/100
Blocked
36%
Avg conflicts / tx
0.47
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,327,114 · 19 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
2w06w08w111w212w113w316w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x232b0b19…d946
0x34b655…2a6f
8 touches
6 conflicts
0x7de57974…f5ba
0x34b655…2a6f
8 touches
6 conflicts
0x92b04c6e…c73d
0x34b655…2a6f
7 touches
6 conflicts
0xf1894e7f…30fe
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xa7481e1f…531f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641d
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641e
0x34b655…2a6f
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 0x232b0b19e0…d1d946
Audit this contract →
← previous block·next block →recent activity