← previous blocknext block →recent activity
Analyzing
Block #102,443,887
16 transactions · 16 stateful · 2026-09-06 10:21:14 UTC
Parallelism
56/100
Blocked
56%
Avg conflicts / tx
1.25
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #102,443,887 · 16 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
1w02w14w25w06w18w210w211w313w414w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfc3648d4…daa2
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xa9988419…9f45
0x34b655…2a6f
10 touches
10 conflicts
0x2c539d94…b63a
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xb6683359…aaec
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
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 0xfc3648d4ef…fbdaa2
Audit this contract →
← previous block·next block →recent activity