← previous blocknext block →recent activity
Analyzing
Block #101,937,639
37 transactions · 32 stateful · 2026-09-04 15:35:40 UTC
Parallelism
78/100
Blocked
53%
Avg conflicts / tx
1.03
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #101,937,639 · 37 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
1w02w03w14w05w16w28w010w011w113w116w119w320w221w322w324w429w133w434w535w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51fc8795…126f
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xb75367ff…a2b7
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
6 touches
3 conflicts
0x93aaefce…5be5
0x34b655…2a6f
6 touches
3 conflicts
0x987859be…2686
0x34b655…2a6f
6 touches
3 conflicts
0xa3fd2e5c…4510
0x34b655…2a6f
6 touches
3 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 0x51fc8795c8…57126f
Audit this contract →
← previous block·next block →recent activity