← previous blocknext block →recent activity
Analyzing
Block #102,215,545
15 transactions · 14 stateful · 2026-09-05 15:04:29 UTC
Parallelism
67/100
Blocked
36%
Avg conflicts / tx
0.53
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #102,215,545 · 15 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w06w18w09w111w213w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x46c14e01…ff09
0x34b655…2a6f
6 touches
3 conflicts
0x711ceb8d…5202
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x2e21046b…5e16
0x34b655…2a6f
6 touches
3 conflicts
0x3e3f27ce…580c
0x34b655…2a6f
4 touches
1 conflict
0x3f5831e5…02b2
0x34b655…2a6f
4 touches
1 conflict
0x6266e26a…96ee
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity