← previous blocknext block →recent activity
Analyzing
Block #102,189,821
11 transactions · 10 stateful · 2026-09-05 12:54:06 UTC
Parallelism
64/100
Blocked
30%
Avg conflicts / tx
0.36
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,189,821 · 11 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
1w02w13w24w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x32e1d03e…68a7
0x34b655…2a6f
6 touches
3 conflicts
0xfa805f95…72a4
0x34b655…2a6f
6 touches
3 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
6 touches
3 conflicts
0x5f749304…d1c1
0x34b655…2a6f
4 touches
1 conflict
0x9bff3222…a246
0x34b655…2a6f
4 touches
1 conflict
0x9c088939…ddd7
0x34b655…2a6f
4 touches
1 conflict
0xa90eb29b…2cec
0x34b655…2a6f
4 touches
1 conflict
0xc4f2b9b5…8a71
0x34b655…2a6f
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 0x32e1d03e9d…d168a7
Audit this contract →
← previous block·next block →recent activity