← previous blocknext block →recent activity
Analyzing
Block #101,325,847
16 transactions · 16 stateful · 2026-09-02 12:15:55 UTC
Parallelism
69/100
Blocked
44%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,325,847 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w17w08w111w112w214w315w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xbc2de485…918d
0x34b655…2a6f
6 touches
3 conflicts
0xd6971ec6…ae0f
0x99c7a7…8bf0
4 touches
1 conflict
0xf4f341bc…c976
0x754704…b603
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x44330547…f55e
0x851145…3f07
4 touches
1 conflict
0x4940258b…0b39
0x851145…3f07
4 touches
1 conflict
0xa1108e25…d2d7
0x99c7a7…8bf0
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity