← previous blocknext block →recent activity
Analyzing
Block #102,006,749
10 transactions · 9 stateful · 2026-09-04 21:26:14 UTC
Parallelism
60/100
Blocked
33%
Avg conflicts / tx
0.3
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,006,749 · 10 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w07w18w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb75367ff…a2b7
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x5746581b…0cb1
0x34b655…2a6f
4 touches
1 conflict
0x74b835e1…b1bd
0x34b655…2a6f
4 touches
1 conflict
0x46d123af…ee81
0x34b655…2a6f
2 touches
0 conflicts
0x5c7b5ec0…0764
0x34b655…2a6f
2 touches
0 conflicts
0x6823c28e…594c
0x34b655…2a6f
2 touches
0 conflicts
0x79ec4509…1f61
0x34b655…2a6f
2 touches
0 conflicts
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
1 conflict on slot 0xb75367ffdb…6fa2b7
Audit this contract →
← previous block·next block →recent activity