← previous blocknext block →recent activity
Analyzing
Block #102,741,415
33 transactions · 25 stateful · 2026-09-07 11:25:11 UTC
Parallelism
88/100
Blocked
40%
Avg conflicts / tx
0.48
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,741,415 · 33 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
7w09w110w011w112w213w315w016w123w024w125w229w030w131w232w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x3d3fa524…c167
0xd32edf…ff58
7 touches
6 conflicts
0x014e90b3…470f
0x34b655…2a6f
4 touches
1 conflict
0x02e8deae…1141
0x34b655…2a6f
4 touches
1 conflict
0x74e485b1…d380
0x34b655…2a6f
4 touches
1 conflict
0x793aa64d…b09c
0x34b655…2a6f
4 touches
1 conflict
0x793aa64d…b09d
0x34b655…2a6f
4 touches
1 conflict
0xa2170810…3ef1
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity