← previous blocknext block →recent activity
Analyzing
Block #101,935,273
18 transactions · 17 stateful · 2026-09-04 15:23:36 UTC
Parallelism
78/100
Blocked
53%
Avg conflicts / tx
0.72
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,935,273 · 18 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
1w02w13w24w05w18w113w214w315w316w117w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
0x67043b0b…97d7
0x34b655…2a6f
6 touches
3 conflicts
0xc9d92517…c787
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0x656c2e3e…a380
0x34b655…2a6f
4 touches
1 conflict
0x65903ef9…2567
0x34b655…2a6f
4 touches
1 conflict
0x6b267bdf…b173
0x34b655…2a6f
4 touches
1 conflict
0x6d1b72ee…6b78
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
3 conflicts on slot 0x51fc8795c8…57126f
Audit this contract →
← previous block·next block →recent activity