← previous blocknext block →recent activity
Analyzing
Block #102,739,523
20 transactions · 20 stateful · 2026-09-07 11:15:40 UTC
Parallelism
80/100
Blocked
35%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,739,523 · 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
1w03w14w07w111w013w114w216w017w118w219w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x1a3d2527…8ca0
0x34b655…2a6f
6 touches
3 conflicts
0xeeb3388a…206e
0x34b655…2a6f
6 touches
3 conflicts
0x290abc80…f605
0x34b655…2a6f
4 touches
1 conflict
0x35b0198e…3e0d
0x34b655…2a6f
4 touches
1 conflict
0x74e485b1…d380
0x34b655…2a6f
4 touches
1 conflict
0x7ce8b3ed…8f54
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity