← previous blocknext block →recent activity
Analyzing
Block #102,018,433
20 transactions · 17 stateful · 2026-09-04 22:25:20 UTC
Parallelism
80/100
Blocked
53%
Avg conflicts / tx
0.75
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,018,433 · 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
1w02w14w15w26w39w214w015w116w118w219w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51fc8795…126f
0x34b655…2a6f
8 touches
6 conflicts
0xddf10453…d774
0x34b655…2a6f
6 touches
3 conflicts
0x173b64af…6c43
0x34b655…2a6f
6 touches
3 conflicts
0x6e7eb884…4fab
0x34b655…2a6f
6 touches
3 conflicts
0x85ca9028…99fc
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
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 0x51fc8795c8…57126f
Audit this contract →
← previous block·next block →recent activity