← previous blocknext block →recent activity
Analyzing
Block #102,283,844
18 transactions · 17 stateful · 2026-09-05 20:50:37 UTC
Parallelism
78/100
Blocked
47%
Avg conflicts / tx
0.78
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,283,844 · 18 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w16w08w012w113w214w315w216w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x39e808d8…ea93
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x77ed432f…fa04
0x065c9d…c394
6 touches
3 conflicts
0x8d412dc0…b9af
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x01477139…97b0
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
3 conflicts on slot 0x39e808d8c2…e1ea93
Audit this contract →
← previous block·next block →recent activity