← previous blocknext block →recent activity
Analyzing
Block #102,269,692
19 transactions · 18 stateful · 2026-09-05 19:38:47 UTC
Parallelism
79/100
Blocked
28%
Avg conflicts / tx
0.42
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,269,692 · 19 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
2w06w07w18w29w313w015w118w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbde524f4…43bf
0x34b655…2a6f
8 touches
6 conflicts
0x839c0c71…bada
0x34b655…2a6f
6 touches
3 conflicts
0x720ae293…6a10
0x34b655…2a6f
6 touches
3 conflicts
0x37c0660b…e0bf
0x34b655…2a6f
5 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x27826bde…1da4
0x34b655…2a6f
4 touches
1 conflict
0x345b6a56…6e3f
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
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 0xbde524f475…b143bf
Audit this contract →
← previous block·next block →recent activity