← previous blocknext block →recent activity
Analyzing
Block #102,210,388
21 transactions · 20 stateful · 2026-09-05 14:38:21 UTC
Parallelism
71/100
Blocked
30%
Avg conflicts / tx
0.43
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #102,210,388 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w18w111w218w319w420w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb637bebe…4cf9
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xeb4304a5…dd06
0x34b655…2a6f
4 touches
1 conflict
0xac27d4e9…fffc
0x34b655…2a6f
4 touches
1 conflict
0xadc848ee…5cb2
0x34b655…2a6f
4 touches
1 conflict
0xb1e0a2b8…8407
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x01315072…0e2d
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 0xb637bebe51…2d4cf9
Audit this contract →
← previous block·next block →recent activity