← previous blocknext block →recent activity
Analyzing
Block #101,321,989
25 transactions · 21 stateful · 2026-09-02 11:56:30 UTC
Parallelism
64/100
Blocked
48%
Avg conflicts / tx
1.24
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #101,321,989 · 25 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w07w18w09w111w013w117w219w320w421w522w623w724w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0xbc8fb280…76a3
0x34b655…2a6f
12 touches
15 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
12 touches
15 conflicts
0xbd590df7…9891
0x34b655…2a6f
10 touches
10 conflicts
0xb0f5d668…99ac
0x34b655…2a6f
10 touches
10 conflicts
0x97394169…cfc0
0x34b655…2a6f
4 touches
1 conflict
0xb17dddfb…96a2
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
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
21 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity