← previous blocknext block →recent activity
Analyzing
Block #102,469,157
26 transactions · 22 stateful · 2026-09-06 12:29:20 UTC
Parallelism
92/100
Blocked
41%
Avg conflicts / tx
0.46
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #102,469,157 · 26 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
1w02w03w04w05w16w07w19w113w014w115w117w123w124w125w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xf5b5f7…6d70
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x0fb999ce…da22
0x754704…b603
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0xff53b6b2…2f57
0x754704…b603
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
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: 0xf5b5f7f8…a36d70
1 conflict on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity