← previous blocknext block →recent activity
Analyzing
Block #102,206,973
12 transactions · 12 stateful · 2026-09-05 14:21:04 UTC
Parallelism
75/100
Blocked
33%
Avg conflicts / tx
0.42
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #102,206,973 · 12 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
1w06w07w18w29w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3f5831e5…02b2
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xd0576b4b…e65e
0x34b655…2a6f
6 touches
3 conflicts
0x1a2055c7…9055
0x34b655…2a6f
4 touches
1 conflict
0x20492d53…80f9
0x34b655…2a6f
4 touches
1 conflict
0x3cf50d44…961b
0x34b655…2a6f
4 touches
1 conflict
0x42e5184f…4e8b
0x34b655…2a6f
4 touches
1 conflict
0x5bfd456e…2ad2
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 0x3f5831e5e5…ee02b2
Audit this contract →
← previous block·next block →recent activity