← previous blocknext block →recent activity
Analyzing
Block #102,305,754
19 transactions · 17 stateful · 2026-09-05 22:41:29 UTC
Parallelism
74/100
Blocked
35%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #102,305,754 · 19 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
1w02w15w08w111w212w313w416w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x86c86181…b16b
0x34b655…2a6f
10 touches
10 conflicts
0x22f10271…841d
0x34b655…2a6f
8 touches
6 conflicts
0xfe2577ac…677b
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x9b9e2a0b…0498
0x34b655…2a6f
6 touches
3 conflicts
0xa7481e1f…531f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
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
10 conflicts on slot 0x86c86181d3…96b16b
Audit this contract →
← previous block·next block →recent activity