← previous blocknext block →recent activity
Analyzing
Block #102,414,522
16 transactions · 16 stateful · 2026-09-06 07:52:33 UTC
Parallelism
63/100
Blocked
44%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #102,414,522 · 16 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
1w02w03w15w18w29w311w412w213w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6554097a…63d2
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…641f
0x34b655…2a6f
10 touches
10 conflicts
0xa33b6d5b…3974
0x34b655…2a6f
8 touches
6 conflicts
0xa4e9800f…4ab0
0x34b655…2a6f
8 touches
6 conflicts
0x56a284d9…32e4
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
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 0x6554097a50…a363d2
Audit this contract →
← previous block·next block →recent activity