← previous blocknext block →recent activity
Analyzing
Block #102,527,327
15 transactions · 14 stateful · 2026-09-06 17:24:24 UTC
Parallelism
80/100
Blocked
21%
Avg conflicts / tx
0.2
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #102,527,327 · 15 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
2w010w011w113w114w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcb06d6a1…b04f
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xeb47a673…6e84
0x34b655…2a6f
4 touches
1 conflict
0x574628e9…dcc3
0x34b655…2a6f
4 touches
1 conflict
0x3e69adfb…3b62
0x34b655…2a6f
2 touches
0 conflicts
0x53f07553…b2d0
0x34b655…2a6f
2 touches
0 conflicts
0x589605bf…7f62
0x34b655…2a6f
2 touches
0 conflicts
0x692e7382…d831
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 0xcb06d6a15e…00b04f
Audit this contract →
← previous block·next block →recent activity