← previous blocknext block →recent activity
Analyzing
Block #102,738,670
14 transactions · 14 stateful · 2026-09-07 11:11:22 UTC
Parallelism
50/100
Blocked
50%
Avg conflicts / tx
1.5
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #102,738,670 · 14 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w18w19w210w311w412w513w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51fc8795…126f
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0xb75367ff…a2b7
0x34b655…2a6f
10 touches
10 conflicts
0x7dd96c96…7335
0x34b655…2a6f
10 touches
10 conflicts
0xe93e862c…b23b
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x3ae9e2da…3e37
0x34b655…2a6f
4 touches
1 conflict
0x9b4f173c…94e6
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
15 conflicts on slot 0x51fc8795c8…57126f
Audit this contract →
← previous block·next block →recent activity