← previous blocknext block →recent activity
Analyzing
Block #102,053,893
16 transactions · 15 stateful · 2026-09-05 01:24:56 UTC
Parallelism
63/100
Blocked
53%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #102,053,893 · 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
1w02w13w24w37w111w213w314w415w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x173b64af…6c43
0x34b655…2a6f
6 touches
3 conflicts
0xf18803af…e7a5
0x34b655…2a6f
6 touches
3 conflicts
0xddf10453…d774
0x34b655…2a6f
6 touches
3 conflicts
0xeb4304a5…dd06
0x34b655…2a6f
6 touches
3 conflicts
0x01315072…0e2d
0x34b655…2a6f
6 touches
3 conflicts
0x5b1d04b9…fa60
0x34b655…2a6f
6 touches
3 conflicts
0x67043b0b…97d7
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity