← previous blocknext block →recent activity
Analyzing
Block #102,429,641
18 transactions · 18 stateful · 2026-09-06 09:09:12 UTC
Parallelism
83/100
Blocked
39%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #102,429,641 · 18 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w15w07w08w09w111w113w214w215w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbbc4bdf7…c62f
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0xdf352747…7eaf
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xfa98c6e8…0747
0x34b655…2a6f
4 touches
1 conflict
0xfa98c6e8…0748
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
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
3 conflicts on slot 0xbbc4bdf713…b3c62f
Audit this contract →
← previous block·next block →recent activity