← previous blocknext block →recent activity
Analyzing
Block #102,802,468
19 transactions · 18 stateful · 2026-09-07 16:35:24 UTC
Parallelism
68/100
Blocked
56%
Avg conflicts / tx
1.26
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #102,802,468 · 19 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
1w02w13w24w15w27w38w49w011w513w014w116w318w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5c455afd…ce06
0x34b655…2a6f
12 touches
15 conflicts
0x4279a749…b7f8
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xbc12e9d2…d720
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x580c6fe7…0fe4
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…00c9
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
15 conflicts on slot 0x5c455afdfc…27ce06
Audit this contract →
← previous block·next block →recent activity