← previous blocknext block →recent activity
Analyzing
Block #102,871,308
24 transactions · 22 stateful · 2026-09-07 22:21:56 UTC
Parallelism
75/100
Blocked
41%
Avg conflicts / tx
0.63
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #102,871,308 · 24 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
1w02w14w05w06w19w010w111w212w313w421w522w123w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0xe7ad475a…0e41
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x53fe4072…9147
0x34b655…2a6f
4 touches
1 conflict
0xba7b566c…a0ce
0x34b655…2a6f
4 touches
1 conflict
0x359866c7…de7b
0x34b655…2a6f
4 touches
1 conflict
0x324ad7e8…b138
0x34b655…2a6f
2 touches
0 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 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity