← previous blocknext block →recent activity
Analyzing
Block #102,648,450
29 transactions · 26 stateful · 2026-09-07 03:37:27 UTC
Parallelism
79/100
Blocked
38%
Avg conflicts / tx
0.72
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #102,648,450 · 29 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w17w110w012w215w316w417w518w019w123w324w325w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc852b267…9d14
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x3be1a66f…ff2e
0x34b655…2a6f
6 touches
3 conflicts
0x3551aa51…8030
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x1ec36a04…54bc
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
10 conflicts on slot 0xc852b26715…339d14
Audit this contract →
← previous block·next block →recent activity