← previous blocknext block →recent activity
Analyzing
Block #102,171,230
15 transactions · 14 stateful · 2026-09-05 11:19:58 UTC
Parallelism
73/100
Blocked
29%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,171,230 · 15 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
2w03w15w26w09w011w114w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf65c9ad4…88f7
0x34b655…2a6f
6 touches
3 conflicts
0xa0dc2aef…ea3e
0x34b655…2a6f
4 touches
1 conflict
0xd016ba79…a39f
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x36890fff…f3d1
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x5b37bb6b…aaff
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 0xf65c9ad483…3388f7
Audit this contract →
← previous block·next block →recent activity