← previous blocknext block →recent activity
Analyzing
Block #102,672,179
18 transactions · 18 stateful · 2026-09-07 05:36:50 UTC
Parallelism
72/100
Blocked
39%
Avg conflicts / tx
0.72
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #102,672,179 · 18 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
1w03w14w05w26w07w18w29w010w116w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfe4336ac…92d0
0x34b655…2a6f
8 touches
6 conflicts
0x9b4f173c…94e6
0x34b655…2a6f
8 touches
6 conflicts
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x7398a26d…8e4e
0x34b655…2a6f
4 touches
1 conflict
0x7ac9dde0…e2ed
0x34b655…2a6f
4 touches
1 conflict
0xb40e601f…bf98
0x34b655…2a6f
4 touches
1 conflict
0xbbd0a386…7abe
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
6 conflicts on slot 0xfe4336ac0f…d992d0
Audit this contract →
← previous block·next block →recent activity