← previous blocknext block →recent activity
Analyzing
Block #102,267,033
27 transactions · 24 stateful · 2026-09-05 19:25:19 UTC
Parallelism
85/100
Blocked
21%
Avg conflicts / tx
0.3
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,267,033 · 27 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
6w09w110w011w114w015w117w218w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x33d92a52…ac8f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x3a5cd535…3546
0x34b655…2a6f
4 touches
1 conflict
0x7abd0ab1…19ee
0x34b655…2a6f
4 touches
1 conflict
0x8ab8a1d3…c5ac
0x34b655…2a6f
4 touches
1 conflict
0x9a6bc012…7495
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 0x33d92a5213…49ac8f
Audit this contract →
← previous block·next block →recent activity