← previous blocknext block →recent activity
Analyzing
Block #102,656,613
15 transactions · 15 stateful · 2026-09-07 04:18:31 UTC
Parallelism
67/100
Blocked
47%
Avg conflicts / tx
0.87
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #102,656,613 · 15 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w17w08w09w110w212w213w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…641f
0x34b655…2a6f
6 touches
3 conflicts
0x42e5184f…4e8b
0x34b655…2a6f
6 touches
3 conflicts
0x58b27dde…52d1
0x34b655…2a6f
6 touches
3 conflicts
0xbceecf11…0120
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xfdf9a0cc…ec50
0x34b655…2a6f
6 touches
3 conflicts
0x6266e26a…96ee
0x34b655…2a6f
4 touches
1 conflict
0x6266e26a…96ef
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 0xc824469a90…af641f
Audit this contract →
← previous block·next block →recent activity