← previous blocknext block →recent activity
Analyzing
Block #102,050,738
25 transactions · 21 stateful · 2026-09-05 01:08:58 UTC
Parallelism
68/100
Blocked
62%
Avg conflicts / tx
1.24
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #102,050,738 · 25 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w25w310w013w114w215w216w317w420w122w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc8b6d32…6601
0x34b655…2a6f
10 touches
10 conflicts
0x02372d42…1871
0x34b655…2a6f
8 touches
6 conflicts
0x3fb3f2e2…fef3
0x34b655…2a6f
8 touches
6 conflicts
0x4d7aaa4f…a8ec
0x34b655…2a6f
8 touches
6 conflicts
0x51fc8795…126f
0x34b655…2a6f
8 touches
6 conflicts
0x53e08444…d671
0x34b655…2a6f
8 touches
6 conflicts
0x67043b0b…97d7
0x34b655…2a6f
8 touches
6 conflicts
0x7e273bc0…5dbc
0x34b655…2a6f
8 touches
6 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
10 conflicts on slot 0xcc8b6d3248…e46601
Audit this contract →
← previous block·next block →recent activity