← previous blocknext block →recent activity
Analyzing
Block #102,061,844
19 transactions · 14 stateful · 2026-09-05 02:05:13 UTC
Parallelism
68/100
Blocked
57%
Avg conflicts / tx
0.68
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #102,061,844 · 19 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
2w03w14w25w27w29w315w416w518w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd66696e0…0842
0x34b655…2a6f
8 touches
6 conflicts
0x53103bb4…02a1
0x34b655…2a6f
6 touches
3 conflicts
0x109d8a52…a7b7
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x71b395d9…1697
0x34b655…2a6f
6 touches
3 conflicts
0x60974827…f0d3
0x34b655…2a6f
4 touches
1 conflict
0x8f8a1602…5a2f
0x34b655…2a6f
4 touches
1 conflict
0x045532dd…4b7d
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 0xd66696e0dc…230842
Audit this contract →
← previous block·next block →recent activity