← previous blocknext block →recent activity
Analyzing
Block #102,178,695
25 transactions · 21 stateful · 2026-09-05 11:57:45 UTC
Parallelism
68/100
Blocked
38%
Avg conflicts / tx
1.16
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #102,178,695 · 25 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w19w210w312w013w117w418w521w622w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc8b6d32…6601
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x152f8e3d…3da0
0x34b655…2a6f
10 touches
10 conflicts
0x2e37bcee…5415
0x34b655…2a6f
8 touches
6 conflicts
0xd66696e0…0842
0x34b655…2a6f
8 touches
6 conflicts
0xa3bcb72f…bed7
0x34b655…2a6f
8 touches
6 conflicts
0x55efd3c2…303a
0x34b655…2a6f
7 touches
6 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
21 conflicts on slot 0xcc8b6d3248…e46601
Audit this contract →
← previous block·next block →recent activity