← previous blocknext block →recent activity
Analyzing
Block #102,206,710
20 transactions · 19 stateful · 2026-09-05 14:19:44 UTC
Parallelism
75/100
Blocked
42%
Avg conflicts / tx
0.7
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #102,206,710 · 20 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
3w04w15w26w08w110w014w115w016w117w218w319w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb75367ff…a2b7
0x34b655…2a6f
8 touches
6 conflicts
0x51fc8795…126f
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x41c56387…a8f6
0x34b655…2a6f
4 touches
1 conflict
0x8324f200…10c6
0x34b655…2a6f
4 touches
1 conflict
0x894e445b…4b84
0x34b655…2a6f
4 touches
1 conflict
0x93f1d5e2…928f
0x34b655…2a6f
4 touches
1 conflict
0xa735de1d…29b0
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 0xb75367ffdb…6fa2b7
Audit this contract →
← previous block·next block →recent activity