← previous blocknext block →recent activity
Analyzing
Block #102,189,602
18 transactions · 16 stateful · 2026-09-05 12:53:00 UTC
Parallelism
83/100
Blocked
38%
Avg conflicts / tx
0.39
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #102,189,602 · 18 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
3w04w15w28w113w014w115w117w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0bb33e3f…7072
0x34b655…2a6f
6 touches
3 conflicts
0x0ec07cf7…c0c9
0x34b655…2a6f
4 touches
1 conflict
0x216aa502…dfd2
0x34b655…2a6f
4 touches
1 conflict
0x32e1d03e…68a7
0x34b655…2a6f
4 touches
1 conflict
0x3380282c…cf3c
0x34b655…2a6f
4 touches
1 conflict
0x40a2e73d…5272
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x5f749304…d1c1
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 0x0bb33e3fc9…697072
Audit this contract →
← previous block·next block →recent activity