← previous blocknext block →recent activity
Analyzing
Block #102,042,308
22 transactions · 22 stateful · 2026-09-05 00:26:13 UTC
Parallelism
68/100
Blocked
50%
Avg conflicts / tx
0.82
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #102,042,308 · 22 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w06w17w08w113w316w417w518w519w620w121w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8bf661cb…bcd2
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…00c9
0x34b655…2a6f
8 touches
6 conflicts
0xd98afa6e…3364
0x34b655…2a6f
8 touches
6 conflicts
0x987859be…2686
0x34b655…2a6f
8 touches
6 conflicts
0xf7772b49…fc12
0x34b655…2a6f
6 touches
3 conflicts
0x65f011a5…bc6e
0x34b655…2a6f
6 touches
3 conflicts
0x67043b0b…97d7
0x34b655…2a6f
6 touches
3 conflicts
0x6823c28e…594c
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 0x8bf661cb38…d4bcd2
Audit this contract →
← previous block·next block →recent activity