← previous blocknext block →recent activity
Analyzing
Block #102,189,547
16 transactions · 13 stateful · 2026-09-05 12:52:44 UTC
Parallelism
81/100
Blocked
38%
Avg conflicts / tx
0.44
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #102,189,547 · 16 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
1w02w13w26w110w011w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x810bee1d…0817
0x34b655…2a6f
6 touches
3 conflicts
0x61a11641…fef0
0x34b655…2a6f
6 touches
3 conflicts
0x98e2f231…ab6e
0x34b655…2a6f
6 touches
3 conflicts
0x29a58269…011a
0x34b655…2a6f
4 touches
1 conflict
0x32e1d03e…68a7
0x34b655…2a6f
4 touches
1 conflict
0x5f749304…d1c1
0x34b655…2a6f
4 touches
1 conflict
0x6deee578…2a5c
0x34b655…2a6f
4 touches
1 conflict
0x73ae20cb…19f1
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
3 conflicts on slot 0x810bee1da9…b60817
Audit this contract →
← previous block·next block →recent activity