← previous blocknext block →recent activity
Analyzing
Block #103,215,142
24 transactions · 18 stateful · 2026-09-09 03:14:24 UTC
Parallelism
88/100
Blocked
28%
Avg conflicts / tx
0.21
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #103,215,142 · 24 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w18w09w116w017w120w123w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x422d5490…52d9
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x7c68d10b…8386
0x34b655…2a6f
2 touches
0 conflicts
0x9d111397…670d
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x422d549061…1f52d9
Audit this contract →
← previous block·next block →recent activity