← previous blocknext block →recent activity
Analyzing
Block #102,429,840
24 transactions · 21 stateful · 2026-09-06 09:10:12 UTC
Parallelism
79/100
Blocked
38%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #102,429,840 · 24 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
2w03w04w05w18w115w216w318w419w120w021w122w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbba42bda…8cd6
0x34b655…2a6f
8 touches
6 conflicts
0xc87e767e…4bba
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x3ca10617…ef02
0x34b655…2a6f
4 touches
1 conflict
0x3cf50d44…961b
0x34b655…2a6f
4 touches
1 conflict
0x42e5184f…4e8b
0x34b655…2a6f
4 touches
1 conflict
0x42e5184f…4e8c
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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 0xbba42bdaae…248cd6
Audit this contract →
← previous block·next block →recent activity