← previous blocknext block →recent activity
Analyzing
Block #102,323,097
7 transactions · 7 stateful · 2026-09-06 00:09:21 UTC
Parallelism
71/100
Blocked
29%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #102,323,097 · 7 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3bb0b210…5f8d
0x34b655…2a6f
4 touches
1 conflict
0x581b829b…9578
0x34b655…2a6f
4 touches
1 conflict
0x5a55a9d1…e7ce
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0xebe581d8…2696
0x34b655…2a6f
4 touches
1 conflict
0x6d1b72ee…6b78
0x34b655…2a6f
2 touches
0 conflicts
0x7cd9fd28…a158
0x34b655…2a6f
2 touches
0 conflicts
0xa4e9800f…4ab1
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 0x3bb0b2107b…f05f8d
Audit this contract →
← previous block·next block →recent activity