← previous blocknext block →recent activity
Analyzing
Block #102,244,070
20 transactions · 20 stateful · 2026-09-05 17:28:58 UTC
Parallelism
80/100
Blocked
30%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,244,070 · 20 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
1w07w19w210w314w217w018w119w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4c9b66e1…e999
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x30c777f3…bacc
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x6c7c1a4b…5751
0x34b655…2a6f
4 touches
1 conflict
0x6fbc2e5a…e69c
0x34b655…2a6f
4 touches
1 conflict
0x76e02d19…7609
0x34b655…2a6f
4 touches
1 conflict
0xa39c4282…f80a
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 0x4c9b66e121…23e999
Audit this contract →
← previous block·next block →recent activity