← previous blocknext block →recent activity
Analyzing
Block #102,060,851
21 transactions · 20 stateful · 2026-09-05 02:00:11 UTC
Parallelism
81/100
Blocked
50%
Avg conflicts / tx
0.9
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,060,851 · 21 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
1w02w13w14w25w313w014w115w217w318w119w220w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x8cecfed5…f339
0x34b655…2a6f
8 touches
6 conflicts
0xeb1b66a1…ce4e
0x34b655…2a6f
6 touches
3 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
6 touches
3 conflicts
0x9bff3222…a246
0x34b655…2a6f
6 touches
3 conflicts
0x9c088939…ddd7
0x34b655…2a6f
6 touches
3 conflicts
0xab3df58f…531b
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity