← previous blocknext block →recent activity
Analyzing
Block #102,648,424
10 transactions · 8 stateful · 2026-09-07 03:37:20 UTC
Parallelism
70/100
Blocked
38%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #102,648,424 · 10 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
1w03w04w15w29w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x54fe7e99…7139
0x34b655…2a6f
4 touches
1 conflict
0x20b94f7c…2a9b
0x34b655…2a6f
4 touches
1 conflict
0xb634184f…61f0
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x4dffc33e…068d
0x34b655…2a6f
2 touches
0 conflicts
0x5b3f5f22…c1a0
0x34b655…2a6f
2 touches
0 conflicts
0x67043b0b…97d7
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 0x54fe7e9943…507139
Audit this contract →
← previous block·next block →recent activity